What n8n is good at
n8n is a workflow automation platform you can run on your own server or on their cloud. Within the automation work listed on marketing and business automation services, it is the option I recommend when the workflow has branching logic, needs to call an API nobody has built a connector for, or runs at a volume that would make per-task pricing painful.
- Cost at volume. Self-hosted, the cost is your server rather than a per-execution fee, which matters when a workflow runs thousands of times a month.
- Data control. Self-hosting keeps customer data on infrastructure you choose, which is the deciding factor for some healthcare, financial and legal work.
- Real logic. Loops, branches, error branches, sub-workflows and code steps in JavaScript or Python, so a complicated process does not have to be flattened into a linear chain.
- Anything with an API. The HTTP node covers services with no dedicated integration, which in Nepal is most local platforms, from courier tracking to payment gateways.
- AI steps in the same canvas as the rest of the workflow, so a model call sits alongside the checks and the approval step rather than in a separate tool, as described on AI automation services.
What n8n is bad at
- Non-technical maintenance. The canvas is readable but debugging a failed run takes comfort with APIs and JSON. If nobody on your team has that, the maintenance question needs an answer before you choose it.
- Being self-hosted without an owner. A self-hosted instance is a server: it needs updates, backups, monitoring and someone whose job it is. Where that person does not exist, n8n Cloud is the honest recommendation despite the higher running cost.
- Polished connector coverage. The integration list is broad but shallower than Zapier’s in places, so some services need HTTP calls and the authentication set up by hand.
- Marketing-team self-service. Someone in marketing will not casually build their own workflow in it the way they might in Zapier.
What I build on n8n
- Lead capture pipelines from forms, ads and chat into a CRM, WhatsApp and a sheet, with deduplication and routing, as on lead generation automation.
- AI-assisted enquiry triage, extraction and drafting, with confidence thresholds and an approval queue.
- Data pipelines that pull from ad platforms and Search Console into Sheets or a warehouse for automated reports and dashboards.
- Document generation and filing workflows, and reconciliation between two systems that disagree.
- Internal operations workflows behind an internal tool or dashboard: assignment, escalation, reminders and weekly digests.
- Integrations with local services that have an API but no ready-made connector.
When I would pick something else
| Situation | Better choice |
|---|---|
| A non-technical team must maintain it | Zapier |
| Heavy branching but no appetite for servers | Make |
| The CRM should be the centre of everything | HubSpot or GoHighLevel |
| Instagram, Messenger and WhatsApp flows | ManyChat |
| Everything lives in Sheets, Gmail and Drive | Apps Script |
The platform is a means, not a position. I have no reseller relationship with any of these and the choice is made on your stack, your team and your running cost.
How a build runs
- Decide hosting first. Self-hosted or cloud, who owns the server, where the data sits, and what the backup and update routine will be.
- Architecture on one page before any node is placed: trigger, steps, branches, error path and alerting.
- Build in a separate environment with your real credentials stored in n8n’s credential store rather than pasted into nodes, and test with awkward real data.
- Add error workflows. Every production workflow gets an error branch that alerts a person, logs the failure and does not lose the record.
- Go live with monitoring on execution failures, queue depth and credential expiry.
- Document and hand over, including exported workflow JSON, a plain-language description of each workflow and the runbook for restarting the instance.
What you receive
- The n8n instance and every workflow in your ownership, with exported JSON you can import anywhere.
- Credentials stored properly, documented, and held in your accounts.
- Error workflows, alerting and a run log for every production workflow.
- A written description of each workflow in plain language, so a non-technical manager knows what it does and how to pause it.
- Handover training and an optional maintenance arrangement, month to month.
Pricing
Build cost is quoted per workflow and per complexity, and it follows the same shape as the rest of the automation work: a fixed project price, then optional monthly maintenance. n8n’s own licensing and any server or cloud cost are paid by you, in your own name, on their published terms. Nothing is resold and there is no commission.
Next step
Describe the workflow and the systems it touches, and say whether you have someone who could maintain a server. I will come back within four business hours with whether n8n is the right platform for it, and a fixed price if it is.
