n8n bills per workflow execution
Diving deeper into
n8n
n8n increasingly charges for complete workflow executions rather than individual steps or seats
Analyzed 6 sources
Reviewing context
This pricing shift turns n8n from a tool customers buy for access into a meter on how much real work the company is doing. Charging per full workflow run, with unlimited users and steps, lets a team start with one builder and then spread automations across sales, support, IT, and finance without renegotiating seats or worrying that every extra branch, enrichment call, or AI step will spike the bill.1 2 3
- A workflow execution is the whole job from trigger to finish. If a lead hits a webhook, gets enriched, scored by an LLM, routed by rules, written into a CRM, and sent to Slack, n8n counts that as one execution, not five or six separate billable actions. That makes complex production workflows easier to justify internally.1 2
- This is a deliberate contrast with rivals. Zapier prices around tasks, where each successful step or connector call draws from the task pool. Make bills in credits tied to operations and some other usage factors. n8n is positioning itself as cheaper when workflows are long, branching, and AI heavy.2 4 5 6
- The model also fits how n8n lands and expands. Paid cloud plans start with an execution allowance, while self hosted business and enterprise buyers pay for governance, identity, environments, and support once workflows become business critical. Revenue then grows as more departments run more automations, not just as more people log in.2 3
Going forward, this makes n8n look more like infrastructure for agentic work than classic SaaS automation. If AI workflows keep moving from experiments into daily operations, execution based pricing gives n8n a direct claim on that growth and strengthens its pitch against step based automation vendors.2 3 4 5 6
Conversation has been deleted
Start new chat