What is n8n and how does it work?
n8n describes itself as a workflow automation tool with a fair-code license. It connects applications and lets you add AI when needed.
A workflow defines a sequence of operations. Those operations can include checking information and passing it to another application.
Building a workflow can require configuring credentials, reading technical documentation, or writing code. You still need to understand the process and check that the applications can exchange the necessary information.
A business can use n8n to log requests, prepare data for a report, or alert a team when an event occurs. The tool coordinates those steps. Each application remains responsible for the data and actions it manages.
What would an accounts receivable workflow look like?
This example is illustrative; it doesn't describe a client. The accounts receivable team receives a file of overdue invoices and wants to create review tasks without sending collection notices automatically.
- Receive the file. The team supplies the workflow with a file using a connection confirmed during testing. The file contains the invoice ID, customer, balance, and due date.
- Validate the data. n8n checks for required fields and looks for an existing task for each invoice. If information is missing or a record is duplicated, it sends the case for review.
- Create the task. For each valid invoice, the workflow creates a task in the team's tool and saves the task ID it receives. The result is a work queue with traceable records, not a collection decision.
- Handle a failure. If the task tool doesn't respond, the workflow logs the error and alerts the person responsible. Before retrying, it checks whether the task was created to avoid duplicates.
Which automation option fits your process?
The choice depends on where the process happens and how much it needs to change. You can also compare n8n with other automation platforms.
| Option | When it fits | What to check |
|---|---|---|
| Features in your current tool | The process happens inside one application and its rules are simple. | Permissions, limits, and error handling. |
| n8n or another platform | You need to connect applications and control workflow steps. | Connectors, data access, and who will maintain the workflow. |
| Script | A specific technical task needs logic the team can code and maintain. | Tests, error logging, and documentation. |
| Custom software | You need a specialized application with its own interface and rules. | Scope, support, and future changes. |
An n8n workflow can complement an existing application. If you need to build the whole product, consider custom software development.
How do you test whether n8n fits your process?
Test a small scope before automating the entire process. The business team and the technical owner should agree on the expected result and who reviews each case.
- Measure the current process. Record the time from receiving the file to creating the task. Also count the errors and duplicates the team finds. This baseline lets you compare results later.
- Define the scope and assign owners. Choose one input, one destination application, and a verifiable result. Assign a business owner to review cases and a technical owner to maintain the workflow.
- Test real cases. Use representative cases and protect data according to company policies. Include complete records, empty fields, duplicates, and a connection failure. Check that each case reaches the right person.
- Compare and decide. Measure time, errors, and duplicates using the same criteria as the baseline. Also review the time spent correcting problems. If the workflow doesn't improve the process, adjust the scope before expanding it.
What does it take to run n8n in production?
You need authorized access to the applications, someone who knows the rules, and someone who can maintain the connections. Document what the workflow does, what data it uses, and how to stop or recover it.
n8n offers Cloud and self-hosting. With Cloud, n8n manages the service. If you self-host, your organization must install it, configure it, and maintain the infrastructure.
The self-hosted Community edition is free to use, though features vary by edition. Self-hosting still involves infrastructure, security, and technical labor costs.
We haven't independently verified the current Cloud Starter price or execution limit. Check both on the n8n pricing page before signing up. The page also says hosted plan data is stored in Frankfurt, Germany.
Beyond the plan, costs depend on connected applications, workload, and support needs. The timeline depends on system access, data quality, and testing. An integration without documented access can take more work than a workflow with available connections.
To detect failures, configure alerts and logs that identify the affected case. n8n lets you create an error workflow that responds when another workflow fails. Decide who receives the alert and how pending work will be recovered.
Test changes before deploying them to production. The n8n source control guide describes separate development and production environments. You also need to restrict access to credentials and review what information appears in logs.
If you add AI to classify text or draft responses, prepare cases with expected results. Review errors before expanding its use. n8n evaluations let you compare outputs against known cases. For customer-facing responses, also decide who approves them and when a case goes to a person.
The choice between a hosted service and your own server also depends on your data policies. Our guide to n8n Cloud and self-hosting in Colombia covers that decision in more detail.