What n8n actually does
An n8n workflow is a graph of nodes. A trigger node starts it, for example a webhook call, a schedule, a new row in a sheet or an incoming message. Each following node does one job: call an API, transform fields, branch on a condition, wait, or run a snippet of JavaScript. Data flows from node to node as items, and you can inspect the data at every step while you build.
That visibility is the practical difference from writing a script. When a workflow misbehaves you can open the execution, see exactly what each node received and returned, and fix the one step that went wrong.
When n8n is a good fit
n8n earns its place when the work has more shape than a simple one-trigger, one-action recipe.
- Branching and loops: route a lead one way if it is a company and another if it is an individual, or process a list of records one by one.
- Custom logic: a Code node or HTTP Request node covers anything with an API, so you are not blocked when no ready-made connector exists.
- Data control: n8n can be self-hosted, so workflow data stays on infrastructure you choose. That matters for customer data and for some regulated businesses.
- AI steps: language-model calls sit alongside ordinary nodes, so extraction, classification or drafting can be one step in a larger automated process with a human approval in the middle.
- Cost at volume: usage is billed by workflow execution on the cloud plan and unlimited on a self-hosted instance, which changes the maths for high-volume, multi-step flows.
When it is the wrong tool
If the job is one trigger and one action between two popular apps, a simpler tool is cheaper to set up and maintain. If the logic is heavy, performance-critical or needs strict transactional guarantees, it belongs in application code with tests. And if nobody on your side will own the workflow afterwards, a clever automation becomes an unmaintained risk. We say so during scoping rather than building something you should not have.
Self-hosted or cloud
n8n Cloud removes the operations burden: updates, uptime and scaling are handled for you. Self-hosting gives you control over data location and removes per-execution billing, but you own backups, updates, security and monitoring. For a small team with sensitive data and an engineer to look after it, self-hosting is reasonable. For most others, start in the cloud and move later; workflows can be exported and imported.
Note that n8n is source-available under a fair-code licence rather than a standard open-source one. Read the licence terms if you plan to embed it in a product you sell.
A realistic first project
A good first workflow is one repetitive task that happens daily and has a clear definition of done: new enquiry arrives, the details are cleaned and written to your CRM, the right person is notified, and the customer gets an acknowledgement. It is small enough to build in days, visible enough that the team trusts it, and a base to extend. Read how we made workflows reliable enough to leave running in the n8n production guide below.