Explore n8n and check its current features and plans.
Visit n8n- Who this is for
- Teams with a workflow owner who can understand transformations, credentials, and failure recovery.
- What you will leave with
- A small tested workflow and an explicit decision about infrastructure responsibilities.
- Scope of this guide
- Official-documentation review with an editorial pilot design. No live product benchmark or measured customer outcome is claimed. Check current plan access and settings before implementation.
On this page · 7 sections
A team that can maintain technical workflow logic and recovery paths.
A team without operational capacity or a simple need already met by existing tools.
Choose a concrete transformation
Start with a bounded input-to-output job: normalize a submitted record, check it, and prepare a reviewed update in another system. Keep the normal path and exceptions visible. Adding AI to an otherwise deterministic field copy creates a separate evaluation problem.
Decide who runs the infrastructure
n8n offers managed Cloud and self-hosted deployment options. Self-hosting gives the team infrastructure responsibilities; it does not remove the work of running a reliable service. Evaluate deployment separately from the feature tier required by your workflow.
Write the operating responsibility list
For either deployment, assign workflow logic, account access, monitoring, and recovery to named roles. For self-hosting, also assign updates, backups, restoration, capacity, and availability. If these tasks have no owner, keep the pilot in a managed or manual setting while the operating plan is resolved.
Check the exact data boundary
Identify every field that leaves the source, where execution data is retained, and which connected service receives it. Verify the actual nodes or API calls and their permissions. Keep test credentials scoped to the permitted trial and confirm how access is transferred when an operator changes.
Test interrupted and repeated runs
Use synthetic records for missing fields, unexpected types, duplicate inputs, and a connection failure after one destination action succeeds. Confirm the next operator can locate the failed item and resume without repeating completed work. Keep a short recovery runbook beside the workflow.
Compare real operating costs
Check current Cloud or edition allowances, external services, and the team time needed for support. For self-hosting, add infrastructure, backup, updates, and recovery exercises. A low hosting bill does not establish a lower total cost than a managed tool.
Make the choice reversible
Compare the same acceptance cases with Make or an included integration. Keep field definitions and the manual fallback independent of the tool. Retain n8n only when the operating team can maintain the required behavior and its measured value justifies that responsibility.
Choose n8n with an operating model, not just a workflow diagram.
Independent editorial guide based on official documentation. We may earn a commission if you sign up or purchase through an affiliate link. Read our affiliate disclosure.
Visit n8nOfficial sources
n8n: Cloud and self-hosted optionsSource material supports product descriptions; workflow criteria and pilot suggestions are our editorial analysis. Check the current documentation and your account settings before implementation.