n8n review

n8n is a workflow automation platform, available as a hosted Cloud service or as software teams can deploy on-premises or with Docker. It sits between the services and systems a team wants to connect: a workflow coordinates steps, can include AI actions and human approvals, and can be inspected run by run. The visual builder is the main interface, with the option to drop into code when a workflow needs custom logic.

That makes n8n an orchestration layer rather than a general-purpose application framework or an AI model. Teams can use it for repeatable processes, route work across connected tools, and inspect what happened when a run fails. The vendor emphasizes opening individual steps, reviewing past runs, and rerunning a broken step. Those features can make a workflow easier to operate and explain, but they do not remove the need to design error handling or maintain the services it connects to.

The vendor describes a visual workflow builder with the option to drop into code, structured inputs and outputs for AI actions, and integrations with third-party services. It also lists Git-based control, isolated environments, workflow diffs, version history, and multi-user workflows as developer controls. The homepage does not name a programming language, SDK, CLI, or API protocol. Confirm the current API, SDK, and integration documentation for the services and languages in your stack before choosing n8n as an integration layer.

The practical build surface described by the vendor is the workflow editor, code within workflows, and its connected integrations—not a documented SDK-first development model. The vendor says workflows can be inspected step by step, past runs reviewed, and a failed step rerun. That can help with debugging and handover. For automation that depends on a specific REST API, webhook pattern, CLI, or package, check the vendor docs for that exact integration and its behavior; do not assume an integration has the same coverage as a maintained client library.

Community Edition (Self-hosted) costs $0 per month and includes unlimited users, workflows, and executions, limited by your server. It excludes SSO, LDAP, queue mode, admin roles, vendor hosting, and support. For Cloud, Starter is $24 monthly or $20 per month with annual billing; it includes 2,500 executions per month, five concurrent executions, and unlimited steps. Pro is $60 monthly or $50 per month annually, with 10,000 executions and 20 concurrent executions at that tier. Higher Pro tiers go up to 50,000 executions for $120 monthly.

Starter and Pro have hard execution caps, not overages: reaching the limit requires an upgrade. Business (Self-hosted only) starts at $960 monthly or $800 per month annually for 40,000 executions, with higher tiers up to 500,000. An extra Business pack costs $4,800 for 300,000 executions. Enterprise is custom-quoted. Cloud plans have a 14-day trial without a credit card; additional Assistant credit pricing is not published. Self-hosted users also need to budget for their own infrastructure.

The vendor says n8n's source code is available on GitHub and that teams can deploy it on-premises or with Docker. The applicable license and the rights it grants for modification, redistribution, or commercial use should be confirmed in the vendor's current license terms; source availability alone does not establish those rights. Community Edition is the free self-hosted option, while Business is a paid self-hosted plan with features such as SSO/LDAP, multiple environments, Git version control, and queue mode.

The vendor does not publish a data-export path in the published product details, so ask how to export workflows, execution history, and credentials before committing. Workflow definitions may be easier to review and manage with Git-based controls, but migration still means rebuilding connections and checking each integration's behavior in the destination system. Keep credentials and workflow logic documented outside assumptions about portability.

Before relying on n8n for production workflows, check execution volume, concurrency, and what happens at the plan limit. Starter includes five concurrent executions; Pro includes 20 at the 10,000-execution tier, with higher tiers up to 50. Community Edition's capacity depends on the server you operate. Cloud Starter and Pro are hard-capped, so a workflow spike can require an upgrade rather than incurring a published overage charge. The vendor lists audit logs, RBAC, encrypted secret stores, SSO SAML, LDAP, alerts, and log streaming among its security and observability controls; confirm which plan includes each control.

Reddit discussion is mixed on complexity. Some developers describe n8n as useful for repeatable transaction paths and for seeing AI output in run history. Others report that complex workflows can be cumbersome compared with writing Python. Treat workflow visibility as an operational aid, not a substitute for testing external integrations, handling retries, or monitoring the infrastructure. The vendor's plan details list dedicated support with an SLA for Enterprise; Community Edition includes no vendor support.