Before a business process depends on an n8n workflow, choose the edition and host. Give every workflow an error path and a named owner, and put versioning and credential review in place. Documentation from n8n and the public accounts of teams running it point to that order.
When you need this
- A workflow built as a prototype now carries a process customers or finance depend on.
- Several teams build workflows on one instance, and nobody can say who owns each one.
- A workflow failed or produced wrong data, and the team found out from a customer.
Evaluation criteria
Setup: edition and host
Will this run on n8n Cloud or on your own infrastructure, and on which edition?
Look forRecord the hosting decision before the first production workflow. Cloud runs in Frankfurt, with updates on a Stable or Beta track. Self-hosted Community is free for internal use, and Business (€667 a month billed annually) is self-hosted only. Stepstone ran one shared Community instance for four years and moved to Enterprise in early 2025, once credentials were shared across users and workflow ownership had blurred.
Ownership: a named owner per workflow
Who fixes this workflow when it breaks, and who takes over when they leave?
Look forName an owner and a backup in each workflow's description, and group workflows into projects with roles. One former employee on Hacker News watched flows built by non-engineers break after their last owner left, until engineering was asked to fix them.
Reliability: an error path on every workflow
Does every production workflow alert someone when it fails, or when it succeeds with bad data?
Look forSet an error workflow in each production workflow's settings, because error handling is opt-in per workflow, and add a Stop And Error node where wrong data must fail the run. One builder found error coverage on an instance had decayed and a workflow had failed 24 times in 71 hours unnoticed. Another workflow scored every lead zero for six weeks while every run succeeded.
Versioning: history and Git
Can you see what changed in a workflow, and roll it back?
Look forSize workflow history to your plan (1 day on Starter, 5 on Pro), or use Git source control and environments on Business and Enterprise. Without them, Malte Buttjer moved Code node source into Git so changes can be reviewed.
Credentials: shared credentials are shared access
Could a workflow let someone reach a system through a colleague's credentials?
Look forShare credentials only within a project, and review them before a workflow goes live. On Enterprise, an external secret store keeps credentials from being shared user by user. Stepstone's IT security team also runs its own instance for sensitive workflows.
Cost control: count executions each month
Which workflows use the most executions, and why?
Look forTrack production executions in the Insights dashboard, filter triggers before the workflow starts, and set polling intervals on purpose. A schedule every 5 minutes runs about 8,600 times a month.
Questions to ask vendors
- Which workflows would stop a business process if they failed overnight, and who is alerted?
- Do we need Git, environments, or SSO this year, and therefore a Business or Enterprise license?
- Which credentials are shared across projects, and who approved each share?
- How many production executions did we run last month, and which five workflows used most of them?
Red flags
- Production workflows with no error workflow set.
- Workflows owned by someone who has left, or by nobody.
- One admin credential for a production database shared with every builder.
- No version history beyond the plan's default, and no export of workflows.
Products in this piece
Sources
- Official documentation
- 8
- Public source
- 4
- n8n pricing
- n8n docs: Compare editions
- n8n docs: Host n8n
- n8n docs: Update your version (Cloud)
- n8n docs: Handle errors gracefully
- n8n docs: Use source control and environments
- n8n docs: Understand executions
- n8n case study: How Stepstone moved from four early adopters to a 3,000-employee rollout
- Hacker News comment on n8n flows breaking after their owner left (Aug 5, 2026)
- achiya-automation on dev.to: n8n's Error Trigger Is Opt-In. My Bot Gate Failed for 71 Hours and Alerted Nobody. (Aug 24, 2026)
- Qasim Parray: The n8n Workflow That Broke Silently for Six Weeks (Sep 29, 2026)
- Malte Buttjer: Free your Code nodes (Aug 5, 2026)