Canvas & nodes
See your whole workflow. Test it before it runs.
Drag steps onto a canvas and connect them. Dry Run walks the whole flow in your browser with emails, webhooks and AI calls simulated, so you can check the path before you run it for real.
What you get
Built for building, not fighting the editor.
Dry Run, then Run
Dry Run simulates side effects and AI steps in your browser. Run executes on our servers against your real integrations.
Checks before every run
Validation catches a missing trigger, a cycle or a misconfigured node, and marks each node with its status.
Versions you can restore
Every save records a version. Restore an older one (which can itself be undone) or export it as a file.
Import and export
Download any workflow as a .fluxo.json file (secrets removed) and import it into another workspace. You can also import n8n workflows and Make blueprints: common steps are converted, best effort.
Autosave
The canvas saves a few seconds after you stop editing, and when you switch or close tabs.
Keyboard-friendly
Undo and redo, copy and paste, a command palette, snap-to-grid, alignment tools and a minimap.
Edit and Test views
After a run, Test view shows each node's result. Flip back to Edit to keep changing the flow.
Node reference
16 node types. One canvas.
Every workflow starts with one trigger. Everything after it is built from these nodes.
Start
- Trigger
- Where a run starts: Manual, Scheduled, Webhook or App event.
AI
- Agent
- An AI step that can reason over several steps and call an HTTP tool.
- Action: AI Generate
- A single AI prompt as one step in the workflow.
- Observer
- Reviews the run so far and reports on errors, speed and cost.
Logic & data
- Router
- Sends the run down the first route whose conditions match, with a default.
- Validator
- Checks data against rules or a JSON schema, then routes to pass or fail.
- Guardrail
- Blocks or warns on banned terms or fields.
- Transformer
- Maps fields, fills templates and builds clean payloads.
- Loop
- Runs the following steps once per item in a list.
- Memory
- Stores and reads values, optionally across runs.
- Retriever
- Looks up relevant entries from memory or static data.
Connect & deliver
- Action
- HTTP Request, Webhook Call, Send Email or Slack Post.
- Integration
- Calls an API with a connected account or a vault credential.
- Sub-workflow
- Calls another workflow as a step.
- Output
- Publishes the result to a webhook, HTTP endpoint, email or Slack, or generates a file.
People & recovery
- Human Review
- Pauses the run until someone approves or rejects it.
- Error Handler
- Catches failures from earlier steps so you can recover or report them.
Dry Run or Run?
| Aspect | Dry Run | Run |
|---|---|---|
| Where it runs | In your browser | On our servers |
| Side effects | Simulated: nothing is sent | Real: every step executes |
| AI steps | Placeholder output, no key used | Your connected provider key |
| Human Review | You pick the decision to simulate | Waits in the Review Queue |
Good to know
- There's no separate publish step: saving is enough. Schedules and webhooks always use the saved workflow once activated.
- Workflows can't contain cycles. To repeat steps, use a Loop node.
FAQ
Questions, answered.
Do I need to write code?
No. You build on a visual canvas and configure each node in a settings panel. Calling an app without a built-in connection needs its API details for an HTTP Request or Integration step.
What's the difference between Dry Run and Run?
Dry Run runs in your browser and simulates side effects: no emails, webhooks, HTTP writes or Slack posts go out, and AI steps return placeholder output without using your key. Run executes on our servers with real side effects.
Can I undo a bad change?
Yes. Undo works while you edit, and the Versions tab lets you restore any saved version. Restoring creates a new version, so it can be undone too.
Can I import workflows from n8n or Make?
Yes, best effort. Workflows → Import reads n8n workflow exports and Make scenario blueprints, converts common steps (webhooks, schedules, HTTP calls, branches, loops, AI, Slack, email, Google Sheets, HubSpot, Notion, Salesforce) and turns anything else into a placeholder step to rebuild. A report shows what converted. Credentials are never copied. Zapier has no portable export, so Zaps are rebuilt by hand.
How do I repeat steps for every item in a list?
Use a Loop node. It runs the steps after it once per item in an array. Connecting nodes in a cycle isn't allowed.
Open the canvas and build your first flow.
Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.
Free to explore · No credit card · 30-day money-back guarantee on paid plans