Automate Your Business Processes with n8n

If you still have an employee manually copying leads from a web form to Excel, then to the CRM, then to Slack to notify the sales team — you're about three years behind. That flow takes 45 minutes to build in n8n and runs afterwards at zero marginal cost. Here's why n8n has become our default choice at Random Walkers, and how to evaluate it for your own stack.

What is n8n, exactly?

n8n (pronounced "node-eight-node") is an open-source workflow orchestrator created in 2019 in Berlin. It lets you visually connect services (APIs, databases, email, files) via "nodes" and trigger sequences of actions on event, schedule, or webhook. The official cloud version starts at €20/month; the self-hosted version is free under the Sustainable Use License (commercial OK, redistribution restricted).

n8n vs Zapier vs Make: the honest comparison

None of the three is universally better. The right choice depends on volume, need for conditional logic, and sensitivity of the data handled.

• Zapier: simplest, 6,000+ integrations, perfect for 1-2 people. Price climbs fast: €30/month for 750 tasks, €120/month for 2,000. Limited conditional logic. Data always at Zapier (US).
• Make (formerly Integromat): best price/quality ratio, richer visual logic, complex scenarios possible. €10/month for 10,000 operations. Good middle ground. Data hosted in EU.
• n8n: steeper learning curve (closer to code), but self-host possible (full sovereignty), unlimited executions, JavaScript or Python code directly in workflows. Ideal above 5,000 operations/month.

5 n8n workflows that actually pay off

These are the automations we deploy first at our SME clients. Implementation time is our estimate for a confirmed n8n consultant.

1. Multi-channel lead capture to CRM

Trigger: web form, LinkedIn message, or inbound email. Actions: enrichment via Clearbit or Apollo, dedup against existing CRM, lead creation with score, Slack notification to assigned sales rep, sequenced welcome email. Build time: 2 hours. ROI: 5-8 hours per week saved for a 3-person sales team.

2. Banking reconciliation

Trigger: new transfer detected via bank API or Bridge/Tink. Actions: matching against Pennylane/Sage invoices, automatic "paid" marking, email follow-up if unidentified after 48 hours. Build time: 4 hours. ROI: 2-4 hours per week for an accountant.

3. E-commerce ↔ ERP ↔ accounting sync

Trigger: WooCommerce, Shopify, or BigCommerce order. Actions: customer/article creation in Odoo or Zoho Books, PDF invoice generation, email send, accounting entry with auto-detected category. Build time: 6 hours. ROI: near-elimination of double entry.

4. Automated HR onboarding

Trigger: new hire created in Personio or BambooHR. Actions: Google Workspace, Slack, GitHub, Notion account creation; onboarding guide sent; 30/60/90 day interview calendar; manager notification. Build time: 5 hours. ROI: 3-6 hours saved per hire, improved candidate experience.

5. AI-assisted competitor monitoring

Trigger: daily cron. Actions: targeted scraping of 5-10 competitor sites, comparison with previous snapshot, GPT-4 or Claude summary of significant changes, Slack or email delivery. Build time: 8 hours. ROI: replaces half an FTE of manual monitoring, provides versioned history.

Self-hosting n8n: quick setup

For serious volume or sensitive data, self-hosting becomes mandatory. Base configuration fits in a docker-compose file; budget 1 day for a robust prod instance with HTTPS, backups, and reverse-proxy.

# minimal docker-compose.yml
services:
  n8n:
    image: n8nio/n8n:latest
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=n8n.example.com
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://n8n.example.com/
      - N8N_BASIC_AUTH_ACTIVE=true
      - N8N_BASIC_AUTH_USER=admin
      - N8N_BASIC_AUTH_PASSWORD=$N8N_PASSWORD
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_DATABASE=n8n
    volumes:
      - n8n_data:/home/node/.n8n
  postgres:
    image: postgres:16-alpine
    volumes:
      - postgres_data:/var/lib/postgresql/data

Minimum spec: 2 vCPU, 4 GB RAM, 40 GB SSD — about €12/month on Hetzner or Scaleway. Add Caddy or Traefik as reverse proxy for automatic HTTPS.

The real limits of n8n

• Very high volume (>100,000 executions/day): self-hosted version requires Postgres tuning and separate workers. Often simpler to code directly.
• Complex-logic workflows (shared state, distributed transactions): prefer real event-driven architecture (Kafka, Temporal).
• Debugging at scale: visual logs become unmanageable beyond 50 nodes per workflow. Split into sub-workflows or move to code.
• Versioning: Git integration exists (n8n Enterprise) but limited. For strict multi-environment workflows, structure from day one.

90-day adoption plan

1. Days 1-15: audit of manual processes, identify top 3 time sinks.
2. Days 16-30: deploy self-hosted n8n, 2-day training of an internal champion, first simple production automation.
3. Days 31-60: industrialize — deploy 3 priority workflows identified, measure time saved.
4. Days 61-90: skill transfer, documentation, expansion plan to 5-10 additional workflows.