Mooflair builds and runs browser automations. You draw a flow in Studio (a canvas editor like n8n), and the engine runs it in a real Chrome browser, with AI steps, human approvals and a live view you can take over at any time. Typical flows scroll π or Threads and reply or post with AI, find Shopee products and make affiliate links, or check pages every morning.
Start here
| If you want to | Read |
|---|---|
| Run it locally and do a first run | Getting started |
| Understand how the pieces fit | Architecture |
| Look up a term | Glossary |
| Build a flow | Studio β Editor β Nodes |
| Start from a ready-made flow | Templates |
| Run a flow with your accounts on a schedule | Campaigns β Dashboard |
| Operate the engine | Engine β Configuration |
| Work with a team | Workspaces |
Everything in these docs
Overview
- Getting started β engine, app, connect them, datasets, first run
- Architecture β mooflair + engine, request flows, where code lives
- Glossary
- Front page β the public landing page: sections, buttons, where the code lives
- Public site β layout and footer, legal pages, contact, status page, docs, sitemap, business details, announcement and maintenance
Design and code
- Design and code conventions β tokens, status badges, route files, route groups, folder map, naming, screen patterns
Workspaces
- Workspaces β roles and the permission table, switcher, settings, members, invites, engines: each flow, campaign and account locked to one (placement, switching, when engines don't match, engine down, region, lists across engines)
Studio
- Studio β the flow list, the flow page, concepts
- Editor β canvas, nodes, notes and groups, copy/paste, shortcuts
- Layout and windows β canvas tabs, activity bar and sidebar, right and bottom areas, windows on rails, move, hide, reset, remembered per browser
- Canvases β main and your own canvases, agent drafts, locks, colors, Git-style Keep (Squash / Merge / Rebase), Revert, call a canvas with Run flow, node description and who made it
- Node details β parameters, settings, input/output panels, pins
- β
{{ nodes.x.output.y | helper }},vars,now - β test vs real, partial runs, retry, statuses, waiting for you
- β browser tabs, per-browser preview and control, open a browser before a run
- β Manual, Schedule, Webhook, Form, Chat, polling triggers (Gmail, Sheets, Drive, Calendar, Notion, Airtable, IMAP), Telegram, MCP server
- β Flow input, Return, Run flow, called flows, cache, error flows, Convert to flow
- β options (with Show when rules: the campaign form changes with your choices), time limit, timezone, callers, error flow, tags
- β draft, publish, history, restore
- β live editing, who's here, pointers, selections and field presence, code carets, follow and spotlight, cursor chat, runs together, your own undo, offline, snapshots and compaction
- β roles on a flow, the share dialog, general access, guests, expiration, ownership, the flow's link and request page, list filters
- β threads on nodes and the canvas, replies, @mentions, resolve; Suggesting mode, review, accept or reject
- β evaluations against the Return output
- β export and import
- β Ask, Plan, Agent, composer and pinned context, conversations (live, several at once), edit and ask again, works live in its draft or directly, Changes bar, autopilot
Campaigns (Operate)
- β run a published flow with its accounts, options, group and windows; restarts, controls
- β Operate βΊ Browsers: Chrome profiles with their sign-ins and proxy, picked per browser name by campaigns and tests, shared with a window per run
- β stages, Now card, stacks, browsers, records (post, stats, your reply; claims hidden; authors with last reply and count) and row actions, charts, logs, runs
Nodes
- β anatomy, common settings, effect nodes, field kinds, full catalog
- Β· Β· Β· Β· Β· Β· Β· Β· Β· Β· Β· Β· Β·
- β write your own, the runtime SDK
Templates
- Β· Β·
- Β· Β·
- Β·
Dataset
- (data a campaign plugs in; the sign-in and proxy live in its browser) Β· Β· Β· (ready-made posts: write, import a Drive folder, generate with AI) Β· Β· Β· Β·
Monitor
- Β· Β·
Engine
- (containers, the worker, resources and limits: sizes in Admin βΊ Configuration βΊ Resources, a workspace's RAM and CPU limit, the lease, draining) Β· (apps, how a run starts, the scheduler) Β· Β· Β· Β·
Account
- β sign up with a code (stepper), forgot password, name, password, contact (email change, WhatsApp verification), sessions, data export, account deletion
Billing
- β plans and prices, currencies (IDR shown, USD charged), checkout, PayPal Subscriptions, invoices, Settings βΊ Billing, Admin βΊ Billing (grant and change plans without payment)
Messages
- β Mailgun and Beamvia, the queue and message service, templates, webhooks, Delivery βΊ Messages
Admin
- β dashboard, flows, campaigns, runs, logs, users, workspaces, delivery (messages), services and jobs, configuration
Operations
- β the launch checklist, tests, backups (none),
/api/health, the status page, admin alerts, email domain records, secrets, PSE, the PayPal checklist
API and security
- β the run API for nodes, webhook, form, agent stream, the engine's internal API
- β API keys,
/api/v1endpoints and the OpenAPI document, outgoing webhooks, signatures, retries - β secrets, what a run gets, tokens, isolation
What Mooflair can do (summary)
| Area | Highlights |
|---|---|
| Editor | Canvas with 78 built-in nodes in 9 domains, script nodes, notes and groups, command palette, shortcuts, copy/paste as JSON, live editing together (pointers, selections, your own undo, offline), undo |
| Items | n8n-style items along edges: a node runs once per item (or once with all), many edges per dot, joins (Merge A + B), item linking, batches, only-first and always-output settings |
| Data mapping | Expressions with 70+ helpers (text, math, lists, parsing) and item roots (item, index, linked nodes.<id>.output, .items, .count), value picker, drag fields from Schema/Table/JSON, output schemas before any run, pinned items |
| Running | Test runs (effects simulated) and real runs, run this step / from here / selected, retry from failed with the current or original version, pause, skip, stop |
| Watching | Animated canvas (node clocks, green edges, status card, summary card), logs with filters, outputs, live preview with per-browser tabs, view or control |
| Humans | Approvals with auto-approve/reject countdown, interventions in the live view, "Ask a human" on any step, notifications (bell, Discord, Slack) |
| Composition | Flow input / Return / Run flow, called flows inside the run, result cache, error flows, Convert to flow |
| Triggers | Manual, Schedule (cron, timezone-aware), Webhook (auth, CORS, IP allowlist, files, streaming), public Form (12 field types, pages), Chat (widget, uploads, streaming), polling triggers (Gmail, Sheets, Drive, Calendar, Notion, Airtable, IMAP), Telegram, MCP server |
| AI | AI nodes (prompt, JSON, choose, classify, summarize, write, guard), cost per run from key prices, the Studio agent working live in drafts (Keep / Undo) |
| Lifecycle | Draft and publish, version history (by plan, 50 at most), tests, packages, tags and per-person stars |
| Campaigns | A flow run per account set with options, groups that never reply to the same post, windows, restarts, a live dashboard (stages, Now, stacks, browsers, records with row actions, charts) |
| Data | Accounts (π, Threads, Facebook, Shopee), browsers with their sign-ins and proxy, AI keys, post sets (ready-made posts with photos and videos, handed out once per campaign or in rotation), variables, tables scoped per account or group, rolling post/quote/reply limits, the Drive (next-drive: records in mooflair, bytes on the engines (next-drive 8), resumable uploads, trash) |
FAQ
Is Mooflair a hosted service?
Both parts run on your own servers: the mooflair app and one or more engines.
Do I need to code?
No. Templates and built-in nodes cover most flows; are there when you need custom steps.
Does Mooflair work with Threads?
Yes. Add a Threads account (its Instagram login) in Dataset βΊ Accounts and start from a Threads template: Auto Reply (plain, brand or Shopee replies), Auto Post (threads, the Shopee link optionally held back until the thread has reach) or Selector Health. See .
Does a test run touch my real accounts?
It signs in and browses for real, but effect nodes (post, reply, buy) are simulated and tables are only read.
Where do I report what a node outputs?
Each node page lists its fields, output dots and output shape; the Output panel in Node details shows real data after a run.
Does Mooflair work with Facebook?
Yes. Add a Facebook account (its email, phone or username) in Dataset βΊ Accounts and start from Facebook Auto Reply (comments on your News Feed, a post search or your groups: plain, brand or Shopee) or Facebook Auto Post (posts on your profile, the Page you act as or a group, with photos or videos, and can share to groups).
Can the auto post templates post photos and videos?
Yes. The π, Threads and Facebook post nodes take Drive files as Media; the publisher templates take them from a post set's posts or from a Drive folder (shuffled or in order, once each or in rotation).
Can Auto Post and Auto Reply run without Shopee?
Yes. Shopee is a choice: Auto Post's Shopee affiliate is off by default and Auto Reply's Reply with comment replies plainly. Mention the brand adds your brand in either. The campaign form only shows what your choices need: with Shopee off, no Shopee account or Shopee options show. See .