Skip to main content

n8n: self-hosted workflow automation (Zapier, but yours)

n8n is a visual automation tool — connect apps and APIs with a drag-and-drop flowchart. What it does, where it fits, and how to self-host it.

n8n is a visual workflow builder: you drag nodes onto a canvas, wire them together, and it runs the flow on a schedule, on a webhook, or when something happens. Think Zapier or Make, but running on your own server with no per-task pricing.

What it does

  • Connects hundreds of services — HTTP, databases, email, Slack, Google Sheets, CRMs, and a generic "HTTP Request" node that reaches anything with an API.

  • Runs on triggers — a schedule (every 5 minutes), a webhook (POST to a URL), an app event, or a manual click.

  • Transforms data in the flow — filter, rename, merge, loop, branch, and run code (JavaScript or Python) where the built-in nodes are not enough.

  • Handles real integration work — retries, error branches, and credentials stored encrypted on your instance.

Why self-host n8n

  • No task limits. Cloud automation tools bill per "task"; on your own instance you run as many as your server allows.

  • Your data stays put. Credentials and the data flowing through your workflows never leave infrastructure you control.

  • Custom code when you need it. The Code node means you are never stuck when a connector is missing.

Where to use it

  • Ops glue — "when a new order lands, add a row to Sheets, notify Slack, and create a support ticket."

  • Data sync — move records between a CRM, a database and a mailing list on a schedule.

  • Lightweight backends — expose a webhook that does a few API calls and returns JSON, without writing a whole service.

  • Content and monitoring — watch an RSS feed or an API and email or post when something changes.

A 2 vCPU / 2–4 GB VPS runs n8n comfortably. Because it holds credentials for your other systems, treat it as sensitive: keep it behind TLS, use strong auth, and store its encryption key safely. It is usually deployed with Docker.

Good to know about the licence

n8n is source-available, not OSI open source: it uses the Sustainable Use License, which is free for internal use and self-hosting but restricts reselling it as a service. For almost every self-hoster that distinction does not bite — but be aware of it if you plan to host n8n for paying customers.

How to get running

  1. VPS + domain + TLS.

  2. Deploy n8n via Docker (there is an official image) with a persistent volume for its data.

  3. Set a strong encryption key and admin credentials; enable user management.

  4. Build your first workflow on a schedule or webhook, and test the error path, not just the happy path.

  5. Back up the n8n data volume — it holds your workflow definitions and credentials.

Specs: /app-hosting/n8n. Start free on a HostingSwift VPS and size up as your workflow count grows.