N4N FLOW · GATE 24
One trigger. The whole fleet moves.
n4n Flow is the wiring between every app in the fleet. A response lands, an invoice pays, a ticket reopens — and the deal, the follow-up and the ledger entry happen on their own. Triggers, branches and AI steps on one canvas, no glue code.
SPECIMEN · LEAD-ROUTER FLOW
Watch a run take the branch
A quote request lands in Forms and the canvas takes over — an AI step scores the lead, a branch reads the budget, and the right action fires. Big budgets become deals; small ones join the nurture queue. Every step lands in the run log with its timing.
illustrative run · your triggers, your branches, your models
CAPABILITIES · GATE 24
The work between the apps, handled
Triggers from anywhere
Every fleet app is a trigger — a form lands, an invoice pays, a ticket reopens, a row changes. Outside services start runs through inbound webhooks.
Branches that read like sentences
Send each run down the right path with plain comparisons on any field — budget over $5,000, country is Sweden, score above 80. No code between the arrows.
AI steps on your balance
Drop a model call into any flow — score a lead, summarise a thread, extract fields, draft a reply. Billed per token through n4n AI, on the fleet’s one balance.
Schedules for the forgettable
Cron-style runs for the work nobody should have to remember — the Monday digest, the month-end sweep, the Friday backup check.
Retries and error paths
Failed steps retry with backoff; whatever still fails takes a dedicated error path you design. Nothing dies silently in a queue.
A run log you can replay
Every run keeps its full step-by-step trace — inputs, outputs, timing. Re-run from the failed step, not from the top.
ROUTE MAP · WORKS THE FLEET
Three stops on every run
n4n AI
LiveAn AI step is one node on the canvas — score, summarise or draft with any of 240+ models, metered per token to the same balance as everything else.
View the gaten4n Forms
ScheduledForms is the fleet’s favourite trigger — the moment a response lands, the flow that files it, scores it and follows up is already running.
View the gaten4n CRM
BoardingRuns write straight to the pipeline — deals created, owners assigned and follow-up tasks scheduled without a human copying fields between tabs.
View the gate
RUN MANIFEST · GATE 24
A day on autopilot
local time · illustrative
n4n flow · run manifest
GATE 24
- 07:00monday digest ran on schedule · 3 reports mailedon time
- 09:41quote request scored 87 · deal created in CRMrouted
- 13:26invoice paid · thank-you queued · entry posted to Booksposted
- 18:03step 3 retry succeeded · error path stayed quietrecovered
When does n4n Flow board?
Flow is scheduled — announced, not yet open. Email support@n4n.io and we will tell you the day it boards. n4n AI, the fleet’s first departure, is live today at n4n.ai.
Do I need to write code to build a flow?
No. Flows are assembled on a visual canvas — pick a trigger, add branches with plain comparisons, drop in actions and AI steps. Inbound webhooks connect services outside the fleet, still without code.
How are AI steps billed?
An AI step calls the n4n AI gateway like any other client and debits the fleet’s one prepaid balance per token, metered to the micro-dollar. No extra vendor, no second bill, $0 minimum.
What happens when a step fails mid-run?
The step retries with backoff. If it still fails, the run takes the error path you designed, and the full trace — inputs, outputs, timing — is kept so you can re-run from the failed step rather than from the top.
GATE 24 · N4N FLOW · SCHEDULED
Wire it once. Let it run.
One email when Flow opens for boarding — and a fleet that already shares one login and one balance while you wait.
30 apps · 1 login · 1 balance · $0 minimum