Most marketing automation tools make you pay per task and lock your data inside their platform. n8n flips that: it is an open-source, self-hostable workflow engine with 400+ integrations and native AI nodes, so you can run lead enrichment, content repurposing, and follow-up sequences on your own terms. This starter guide walks through the three automations marketing teams actually ship, then combines them into one working template you can build in an afternoon.

Why n8n for marketing work#

n8n connects APIs, databases, webhooks, AI models, and custom code on a visual canvas. Two things set it apart from Zapier-style tools:

  • Self-hosting. The Community Edition is free software (under n8n's Sustainable Use License, source on GitHub) and runs on infrastructure you control via Docker, npm, or Kubernetes. Your data never has to leave your server.
  • Execution-based pricing on Cloud. n8n Cloud charges per workflow run, not per step. A Starter plan is €20/month billed annually (€24 on monthly billing) for 2,500 executions, with unlimited users and unlimited active workflows — so an 8-step lead pipeline costs one execution, not eight tasks. A 14-day trial is available.

Because n8n charges per execution and self-hosting is free apart from server costs, the automations below scale from a hundred to ten thousand leads without the per-task price shock.

Getting set up#

The fastest path: create a new workflow in n8n Cloud, click Add first step, and browse templates. Templates are importable JSON workflows you can customize, which is the quickest way to start. If you prefer self-hosting, install the free Community Edition with Docker and you get unlimited executions — you pay only for a small VPS.

Either way, connect credentials once for the tools you use: your CRM (HubSpot, Salesforce, Pipedrive), Slack, an LLM provider (OpenAI, Anthropic, or a local model), and an enrichment service (Hunter.io for email verification, Apollo.io for company data, or the Lusha community node for contact enrichment). The workflows below assume those credentials exist.

Workflow 1: Lead enrichment and scoring#

This is the highest-value automation for most teams. A bare form submission (name, email, company) becomes a fully qualified, prioritized lead in seconds.

Node chain:

  1. Webhook trigger — receives the form POST. Point your website form's action at this URL.
  2. HTTP Request — sends the email domain to an enrichment API such as Hunter.io for a verified email, or Apollo.io for the prospect's LinkedIn profile and job title.
  3. AI / Code node — scores the lead against your criteria. A Code node with explicit weights is the most debuggable option: for example, +30 for VP-or-above seniority, +20 for a target industry, +10 for a target region, for a 0–100 score. The community's published lead-scoring template routes leads into three tiers — Hot (60+), Warm (35–59), Cold (below 35).
  4. IF node / router — routes by tier:
  • Hot: upsert to HubSpot and push a Slack alert to a #hot-leads channel with the enriched data.
  • Warm: sync to the CRM and post a standard notification.
  • Cold: send to a nurture list, not the active pipeline.
  1. CRM sync — write every record with its score and enrichment data so sales and marketing see the same picture.

Tip from real deployments: use the webhook response to show "Hot" leads a calendar booking link immediately while "Cold" leads get a whitepaper download. And keep scoring logic transparent — the hardest part of this workflow, per teams that run it in production, is scoring rules the sales team actually trusts. Start with deterministic rules in a Code node, then add an LLM call to classify edge cases rather than leading with AI scoring.

Workflow 2: Content repurposing pipeline#

One long-form piece can become a week's worth of channel content, but doing it manually eats a marketer's afternoon. The automation pattern:

  1. Schedule trigger (or a webhook from your CMS) — fires when a new blog post publishes or on a set cadence.
  2. Read the source — HTTP Request pulls the post's text from your CMS API, or a Google Docs node fetches the draft.
  3. AI Agent node — n8n's native AI Agent (current versions use the Tools Agent mode; older agent modes were removed in n8n 3.0, so check any template you import) rewrites the post into derivative assets with strict prompts: three LinkedIn posts, five short-form video hooks, one email-newsletter summary, one set of ad copy variants.
  4. Human review gate — write the outputs to a Google Sheet or Notion page and pause for approval before anything publishes. The part teams spend the most time on, per practitioners, is source citation and human review — automate the drafting, never the sign-off.
  5. Publish — approved assets go through Buffer, the LinkedIn node, or your email tool's node.

The output quality lives or dies by the prompt. Give the agent your brand voice constraints (word counts, banned phrases, formatting rules) in a system prompt stored as a reusable sub-workflow, not scattered across ten workflows.

Workflow 3: Follow-up sequences with reply detection#

Static email sequences send message #3 even after the prospect replied to message #1. In n8n, the whole loop lives in one workflow:

  1. CRM trigger / webhook — a new warm lead enters the sequence.
  2. Enrich first — reuse Workflow 1's data: role, company context, recent activity. Feed that into the LLM call so subject lines and bodies reflect real context instead of {first_name} placeholders.
  3. AI-generated drafts — an LLM node produces a personalized first touch and two follow-ups, written to a log (Google Sheets or your CRM) before anything sends.
  4. Delivery nodes — send via your email tool (Gmail node, Smartlead, or your provider's API). Store message IDs.
  5. Reply detection — a Gmail trigger or polling node watches for replies. When a reply arrives, the workflow stops the sequence for that lead, logs the reply, and notifies the owner. No reply after step 2 → step 3 fires on a Wait node timer.
  6. Suppression rules — the unglamorous part that matters most: a shared "do-not-contact" check (bounced addresses, unsubscribes, existing customers) at the start of every sequence run, so suppression holds across all channels.

The starter template: one workflow, three jobs#

You don't need three separate workflows to start. Here is a single starter workflow that ties all three together in about a dozen nodes:

Form Webhook → Enrich (HTTP Request) → Score (Code node, 0–100)
   ├─ Hot (≥60) ──→ HubSpot upsert → Slack alert + calendar-link response
   ├─ Warm (35–59) → HubSpot upsert → AI draft follow-up → Wait 3 days
   │                    └─ Reply detected? → stop | else send follow-up
   └─ Cold (<35) ──→ Nurture list → Content repurposing drafts (on schedule)

Build it in this order: webhook and CRM sync first (verify data flows end to end), then enrichment, then scoring, then the AI drafting. Test each stage with a dummy submission before activating — failed and test executions don't burn cloud quota, so iterate freely.

Execution budgeting: count executions, not steps. A form-submission workflow that fires 2,000 times a month fits comfortably inside the 2,500-execution Starter allowance. If you poll a trigger every 5 minutes, that's ~8,600 executions a month before any real work happens — prefer webhooks over polling to keep volume under control.

What to watch out for#

  • API rate limits and costs are yours to manage. Enrichment APIs and LLM calls bill separately from n8n. Cache enrichment results in a database so you never pay twice for the same company.
  • Error handling is a feature, not polish. n8n supports retries, rate limiting, and batching at the node level — set them on every HTTP and AI node, because third-party APIs fail at scale.
  • Keep humans in the loop where it counts. Automated publishing without review is how a brand-voice slip becomes a public embarrassment. Enrich and draft automatically; review and send deliberately.
  • Suppressions before sends. One shared do-not-contact check per sequence is the difference between automation and spam infrastructure.

Takeaway#

n8n's real advantage for marketing isn't the node count — it's ownership. Self-host and you pay only for a server while your data stays in your hands; use Cloud Starter and you get a flat €20/month (annual billing) for 2,500 full workflow executions, regardless of how many steps each run contains. Start with the lead enrichment and scoring workflow, since it pays back immediately in sales follow-up speed, then layer content repurposing and context-aware follow-ups onto the same data. Build the webhook and CRM sync first, verify with test submissions, add enrichment and scoring next, and only then hand the drafting pen to the AI — with a human holding the publish button.