How to Set Up Your First n8n Workflow in 20 Minutes
You get a working n8n workflow in about 20 minutes: install it with Docker or start the 14-day cloud trial, add a Webhook node, pass the data through a Set node, and finish with a Slack message. No code required, though a passing familiarity with JSON helps a lot.
n8n is a fair-code automation platform you can self-host for free or rent by the workflow execution. That distinction matters more than any feature list, because the pricing model quietly decides how you build.
What does n8n actually cost in 2026?
Self-hosting the Community Edition is free, forever, with no execution cap. Cloud plans start at €20 a month (billed yearly) for 2,500 executions on the Starter tier, and the €50 Pro tier adds 10,000 executions plus 5 active workflows that can run in parallel.
Sounds cheap until you count executions properly. One execution equals one full workflow run, regardless of how many nodes fire inside it. A workflow with 200 nodes still costs one execution. That is genuinely different from Zapier, which bills per task and can burn 40 tasks on a single run.
| Plan | Price | Executions/month | Notes |
|---|---|---|---|
| Community (self-host) | Free | Unlimited | You run the server, backups and upgrades |
| Starter (cloud) | €20/mo yearly | 2,500 | 5 active workflows |
| Pro (cloud) | €50/mo yearly | 10,000 | Adds parallel execution |
| Business (cloud) | €800/mo yearly | 40,000 | SSO, environments |
For a team doing fewer than 2,500 runs a month, cloud Starter is the sane default. Above that, a €5 VPS will outrun any cloud plan.
Should you self-host or use n8n Cloud?
Self-host if you have one person who can patch a Docker container and you handle customer data that should not leave your servers. Use Cloud if you have no ops coverage and you want webhooks that stay online at 3am.
If you are unsure, start on Cloud. Migrating to self-hosted later takes one afternoon: export workflows as JSON from the Cloud UI, import them into your instance, then re-enter credentials because secrets are encrypted per instance and do not survive export.
Self-hosting has three requirements worth knowing before you begin:
- A server with at least 1 GB RAM (2 GB if you use the AI nodes)
- Docker or Docker Compose installed
- A public URL with HTTPS if you want webhooks from Slack, GitHub or Stripe to reach you
The HTTPS part trips people up. Running n8n on http://localhost:5678 is fine for manual runs, but external services need a reachable address. Cloudflare Tunnel is the quickest fix and costs nothing.
How do you run the Docker install?
Run one command. That is the whole install for a quick trial.
docker run -it --rm --name n8n -p 5678:5678 \
-v n8n_data:/home/node/.n8n \
docker.n8n.io/n8nio/n8n
Open http://localhost:5678, create the owner account, and you are inside the editor. The named volume n8n_data keeps your workflows after a restart. Forget that flag and every container restart wipes your work, which is the single most common first-day complaint.
For anything past a trial, write a Compose file with the volume mounted explicitly and restart policy set to unless-stopped. Production also needs N8N_ENCRYPTION_KEY set to a fixed value, otherwise credentials become unreadable if the volume is ever rebuilt.
How do you build a workflow that sends Slack a message from a webhook?
Four nodes, one connection each. The fastest way to learn how data moves through n8n.
- Create a new workflow and click the plus button on the canvas.
- Add a Webhook node, set the HTTP method to POST, and copy the test URL.
- Add a Set node after it and map one field, for example
textfrom{{ $json.message }}. - Add a Slack node, pick Send Message, connect a credential, and put
{{ $json.text }}in the message field. - Click Listen for Test Event on the webhook, then fire a request:
curl -X POST https://your-url/webhook-test/abc -H "Content-Type: application/json" -d '{"message":"hello from n8n"}' - Check the Slack channel, then hit Activate to swap the test URL for the production one.
The test URL only listens once, for two minutes. The production URL fires whenever the workflow is active. Mixing those two up causes the classic “my webhook works then stops” bug report.
What are the most common mistakes in a first build?
Connecting nodes left to right but forgetting the data path. n8n passes arrays of items, not single objects. If an upstream node returns 12 items, the downstream Slack node fires 12 times. Fix it by adding a Limit node or switching the operation to run once.
Using expressions with the wrong prefix. Old tutorials show {{$node["Webhook"].json["name"]}}. That syntax still resolves but is deprecated; the current form is {{ $('Webhook').item.json.name }}. Copy old tutorials and you can spend an hour chasing an undefined value.
Ignoring the execution log. Every run is stored with input and output per node. When something fails, open Executions, click the failed run, and click the exact node in red. The error message there is far more useful than the toast notification.
Who should skip n8n?
If you want a tool that works without you ever touching a server, n8n will irritate you. It is developer-shaped: half the documentation assumes you know what an OAuth2 refresh token is.
Non-technical marketing teams usually do better on Make.com or Zapier, which host everything and cost less at very low volume. Solo founders automating three steps once a week do not need n8n at all.
Quick Summary
- n8n is a self-hostable, fair-code automation platform; Community Edition is free with unlimited executions.
- n8n Cloud starts at €20/month (yearly billing) for 2,500 executions.
- One execution = one full workflow run, not one task, which makes it cheaper than Zapier at volume.
- A first webhook-to-Slack workflow takes about 20 minutes and four nodes.
- Always mount a persistent volume and set N8N_ENCRYPTION_KEY before running anything you care about.
