n8n is an automation platform — think Zapier or Make, but with more control and a self-hosted option that keeps your data on your own infrastructure. If you’ve been stringing together tools manually or paying for a Zapier plan that’s running out of tasks, n8n is worth understanding. Here’s what it actually is, how it compares, and how to build your first workflow without a developer.

What n8n Is (and Isn’t)

n8n is a workflow automation tool. You build workflows visually by connecting nodes — each node is either a trigger (something that starts the workflow), an action (something that does work), or a logic step (a filter, transformation, or branch). It connects to over 400 apps and services, has built-in AI nodes for calling models like GPT or Claude, and lets you write custom JavaScript when you need something that doesn’t exist as a node.

What it isn’t: a magic button that automates your whole business out of the box. You need to design the workflow, connect the accounts, and test it before it runs unattended. The payoff is workflows that run reliably without you touching them every time.

Self-Hosted vs. n8n Cloud

n8n gives you two options:

• n8n Cloud — hosted by n8n, no server setup required, starts at around $20/month. Best choice if you want to get started quickly and don’t have specific data residency requirements.
• Self-hosted — you run n8n on your own server (a $6/month VPS from Hetzner or DigitalOcean works fine for most SMB use). Requires a bit of setup, but your data never leaves your infrastructure. Worth it if you’re handling sensitive customer or financial data.

For most operators just getting started: use n8n Cloud. Switch to self-hosted when you have a reason to.

Your First Workflow: Trigger → AI Step → Action

Here’s a simple, real workflow to build on day one — automatically summarizing new support emails and posting to Slack:

1. Add a Gmail trigger node — set it to watch for new emails in your support inbox
2. Add an OpenAI or Anthropic node — pass the email body and ask it to summarize the issue and suggest a response category
3. Add a Slack node — post the summary to your #support channel with the sender’s name and a link to the original email
4. Save, activate, and test it with a real email

Total build time for this workflow: 30–45 minutes your first time. Once it runs, it runs every time without you doing anything.

Where Automation Pays Off

Not everything is worth automating. Focus on workflows that are: repetitive (happen multiple times per week), consistent (the same inputs always produce the same kind of output), and low-risk if something goes slightly wrong. High-ROI starting points for most businesses:

• Lead notifications — new form submission → enrichment → Slack alert to sales
• Invoice reminders — trigger from accounting software → draft email → send or queue for review
• Content repurposing — new blog post → AI reformats for LinkedIn → saved as draft in Buffer
• Weekly report generation — pull data from Google Sheets → AI summary → email to leadership

Keeping a Human in the Automation Loop

The most common mistake in automation: setting something to run fully autonomously before you’ve seen it fail. Start every new workflow with a human review step — route the output to a Slack message or a draft folder before it takes any real action. Run it that way for a week, review the outputs, fix what’s off, then remove the review step only when you’re confident it’s working correctly. Automation earns autonomy — it doesn’t start with it.