Want Mooflair to do something on a website for you, like read a page every morning, save a list into a table, sign in and fill a form, or let AI write something you approve first? These guides show you how, click by click, on real public websites you can open right now.
A flow is a set of steps (nodes) joined by lines. A trigger starts it, browser nodes act on the page like a person would, and data, AI and human nodes do the rest. You build it on the canvas in Studio, try it with Test run, then Publish it so it runs by itself.
The guides, in order
| # | Guide | You build | You learn |
|---|---|---|---|
| 1 | Your first flow | Open a page, read its headline, send it to your bell | Creating a flow, adding and connecting nodes, Test run, Logs and Output |
| 2 | Find the right element | Selectors for any website | Chrome DevTools, CSS, text= and role= selectors, testing one step |
| 3 | Save a list into a table | Every story on Hacker News's front page, saved without duplicates | Extract a list, Loop over items, Data table |
| 4 | Sign in and fill a form | A sign-in on a practice site, checked and reported | Fill a form, secret variables, Wait for URL, signing in by hand, captchas |
| 5 | Add AI and your approval | A short AI note per story that you approve before it's saved | AI keys, the Prompt node, Approval |
| 6 | Put it on a schedule | The flow running every morning by itself | Publish, Schedule, the Runs page, fixing a failed run |
New to all of this? Start at guide 1. Each guide takes 10 to 20 minutes, and each one builds on the guide before it.
Before you start
- A Mooflair account. Sign up, and Mooflair creates your workspace for you.
- Chrome on your computer (for guide 2). You'll use its Inspect tool to find elements on a page.
- An AI key (for guide 5). OpenAI or DeepSeek. The guide shows you where to add it.
You don't need to write code. Every step is a node you pick from a list and fill in.
Where things are in the app
| You want to | Go to (left sidebar) |
|---|---|
| Build and run flows | Studio › Flows |
| See every run of every flow | Operate › Runs |
| See and sign in to your browsers | Operate › Browsers |
| Keep data between runs | Dataset › Tables |
| Store a password or a value that every flow can use | Dataset › Variables |
| Add an AI key | Dataset › AI |
| Read what your flows told you | the bell (Notifications) at the top |
Words you'll meet
| Word | Meaning |
|---|---|
| Node | One step: open a page, click, read text, ask the AI, save a row. |
| Dot | A connection point on a node. Output dots are on the right (some nodes have more than one, like Next and Not found), and the input dot is on the left. |
| Item | One piece of data moving along a line. Most nodes run once for each item they get. |
| Expression | {{ … }} in a field. It puts in a value from an earlier step, like {{ nodes.extract.output.value }}. |
| Selector | How a node finds an element on the page, like h1 or #username. |
| Test run | A run that doesn't post, reply or buy (effect nodes ⚡ are skipped) and keeps its table rows apart as test data. |
| Publish | Makes your current draft the live version that triggers (Schedule, Webhook, Form) run. |
The full list is in the .
Want a head start?
Templates are ready-made flows for 𝕏, Threads, Facebook and Shopee. In Studio › Flows › New flow, pick one under Or start from a template. See .
FAQ
Do I need to know how to code to build a flow?
No. Every step is a node with fields you fill in. Guide 2 teaches you the one technical part, picking an element on a page, with Chrome's Inspect tool.
Which websites can a flow work on?
Any site you can open in Chrome. The flow drives a real Chrome browser, so it sees the page just like you do. Respect each site's terms and don't go faster than a person would.
Will a test run post or buy anything?
No. In a test run, effect nodes (marked ⚡, like post, reply or buy) don't act. They hand on { "dry": true } instead. Opening pages, clicking and reading still happen for real.
What's the difference between Test run and Run?
Test run is for trying a flow safely. Run acts for real, and it asks you to confirm first. Both use your draft. Once you publish, triggers run the published version.