Quick Answer
60-second read
Getting started with n8n means choosing between cloud (faster setup, official support, from €20/month) and self-hosted (free forever, unlimited executions, but you manage the server). This guide covers both paths: sign up for cloud or install self-hosted via Docker, then build your first workflow by adding a trigger, adding actions, testing with sample data, and activating it. Most first-time users have a working automation within an hour on cloud, or a bit longer on self-hosted once the server is running.
Free cloud trial, or self-host for free forever
This tutorial was last updated July 2026, walked through directly on n8n’s current cloud and self-hosted setup.
Option A: Setting Up n8n Cloud
The faster path — no server to manage, official support included.
Step 1: Sign Up for n8n Cloud
Go to n8n’s signup page and start a free trial — no credit card required to explore the interface and build your first workflow. Cloud plans start at €20/month if you decide to continue after the trial.
Option B: Self-Hosting n8n (Free, Open-Source)
The free path — unlimited executions forever, but you manage your own server.
Step 1: Set Up a Server With Docker
Provision a small VPS (budget roughly €5-20/month depending on provider and workflow volume) and install Docker if it isn’t already available. n8n’s own documentation provides a ready-to-use Docker command that pulls and runs the Community Edition with minimal configuration.
Step 2: Access Your Self-Hosted Instance
Once running, access the n8n editor through your server’s IP address or domain in a browser, and complete the initial account setup (admin email and password). From here, the workflow-building experience is identical to cloud — only the hosting differs.
Building Your First Workflow (Cloud or Self-Hosted)
Step 1: Add a Trigger Node
Click “Add first step” and choose what should start your workflow — a webhook, a schedule, or an app event (like a new form submission). This is your trigger node, the entry point for everything that follows.
Step 2: Add Action Nodes
Click the “+” after your trigger to add the next step — an app action, a code node (JavaScript/Python), or a logic node (filter, conditional branch). Map data from earlier nodes into each new node’s fields using n8n’s expression syntax, which references outputs from previous steps.
Step 3: Test With Sample Data
Run the workflow manually and inspect each node’s output as it executes. This is where n8n’s execution log becomes valuable — you can see exactly what data flowed into and out of each step, making it much easier to catch mapping errors before going live.
Step 4: Activate the Workflow
Toggle the workflow to “Active” so it runs automatically whenever the trigger fires, without further manual action. Check the execution history periodically, especially in the first few days, to confirm it’s behaving as expected on real data.
Common Beginner Mistakes to Avoid
- Skipping the template library — n8n’s pre-built workflow templates can save significant time versus building common automations entirely from scratch while you’re still learning.
- Not testing each node individually — n8n’s step-by-step execution view exists specifically to isolate where a workflow breaks; use it instead of guessing.
- Relying solely on cloud for business-critical automations — given documented reports of unexpected cloud account issues, consider a self-hosted fallback for anything truly mission-critical; see our full n8n review for the specific risk details.
- Underestimating the learning curve — budget realistic time (days, not hours) to get comfortable with node-based logic and data expressions before expecting to move fast.
Next Steps
Once you’re comfortable building workflows, it’s worth knowing how n8n compares to more beginner-friendly alternatives. See our n8n vs Zapier comparison to understand exactly where n8n’s added complexity does (and doesn’t) pay off, or our original Make vs n8n comparison for a deeper look at execution-based vs credit-based pricing.
Frequently Asked Questions
Should I start with cloud or self-hosted n8n?
Start with cloud if you’re new to n8n — it’s faster to set up (no server management) and lets you evaluate the tool before committing to self-hosting infrastructure. Switch to (or add) self-hosting once you know n8n fits your needs and you want to eliminate recurring costs or need full data control. Many experienced teams develop on cloud and run production workflows self-hosted, specifically to avoid any cloud-account risk on business-critical automations.
Do I need a server to self-host n8n?
Yes — a VPS or server running Docker (the simplest, most common method) or Node.js directly. Budget roughly €5-20/month for a small server, depending on your workflow volume and provider. This is genuinely less involved than it sounds if you’re comfortable with basic command-line setup, but it is a real technical step that cloud users skip entirely.
What is a ‘node’ in n8n?
A node is a single step in your workflow — a trigger (what starts the workflow), an action (what it does, like sending an email or updating a spreadsheet), or a logic step (like a filter or conditional branch). Workflows are built by connecting nodes together visually, which is where n8n’s learning curve mostly lives — understanding how data flows and transforms between connected nodes.
Can I import existing automations or templates into n8n?
Yes — n8n has a public template library with pre-built workflows you can import and customize rather than building from scratch, which is a genuinely useful shortcut for common automation patterns while you’re still learning the node-based interface.
How do I debug a workflow that isn’t working?
Use n8n’s execution log to see exactly which node failed and what data it received, rather than guessing. Run the workflow manually with test data first, and check each node’s output individually before assuming the whole workflow is broken — most issues trace back to one specific node’s data mapping, not the overall design.
Related Resources
- ⚙️ n8n Review 2026 — Full hands-on review, pricing, and verdict
- ⚙️ n8n vs Zapier — Technical flexibility vs non-technical accessibility
- ⚙️ Make vs n8n — Our original, detailed comparison between these two tools
- 🔗 Pabbly Connect vs Zapier — Another automation option compared
- ⚙️ Make vs Zapier
- ⚙️ How to Use Make.com
- 🔗 Pabbly Connect Review
- 🔗 Pabbly Connect vs Make.com
- 🔗 How to Use Pabbly Connect
