How to Automate Lead Generation with n8n (2026 Step-by-Step)

Last updated September 2026 · ~8 min read · by StackHonest

Affiliate disclosure: some links below are affiliate links. If you sign up through them I earn a commission at no extra cost to you. The build below is assembled from n8n's own documented nodes and the vendors' current pricing pages.

Short answer: build a 3-node n8n workflow -- a Form or Webhook trigger to catch the lead, an HTTP Request or dedicated CRM node to push the contact record, and a Twilio/WhatsApp/email node to fire an instant follow-up. Self-hosted, this costs nothing beyond a 5-6 dollar/mo VPS since executions are unlimited. On n8n Cloud it fits comfortably inside the 20 dollar/mo Starter tier's 2,500 monthly executions unless your trigger fires on a tight recurring schedule rather than only on real leads.

Prerequisites and real costs

You need three things: an n8n instance (self-hosted free + VPS, or Cloud starting at 20 dollars/mo annual per my full n8n review), a place leads come from (a website form, a Facebook lead ad, or a Google Sheet someone else fills in), and a destination (a CRM, a spreadsheet, or just a Slack/email alert if you are not ready for a full CRM). If you have zero budget: n8n's Form trigger node can BE your form, so you can skip a separate form tool entirely and pay nothing but the VPS. If you already pay for Typeform, Tally, or a website form plugin, keep it and just point its webhook at n8n.

Step-by-step build

Create the trigger. Add either an n8n Form node (fastest, zero extra tooling) or a Webhook node if your existing form/landing page can POST to a URL. The Webhook node gives you a unique URL the moment you save it -- paste that into your form tool's "send to webhook" setting.
Capture and normalize the data. Add a Set/Edit Fields node right after the trigger to rename incoming fields to a consistent shape (name, email, phone, source) -- this saves you rewiring every downstream node later when a form field name changes.
Push to your CRM. Use the dedicated node if your CRM has one (HubSpot, Pipedrive, Airtable all have native n8n nodes), or an HTTP Request node against the CRM's API if it does not. Map the normalized fields from step 2 into the CRM's required fields.
Add a condition for hot leads. An IF node checking something like "budget field is not empty" or "source = phone call" lets you branch high-intent leads into a faster follow-up path versus a standard nurture path.
Fire the instant follow-up. A Twilio node (SMS), WhatsApp Business node, or plain email node sends the text-back or confirmation within seconds of form submission -- this single step is usually the highest-leverage part of the whole workflow, since response speed correlates directly with lead conversion.
Test with a real submission, not the "execute workflow" button. Submit an actual test lead through the real form or webhook URL at least once before trusting it -- the manual test-run inside the n8n editor skips some header/payload quirks that show up only on a live POST.

Common failure points

Field name mismatches. The single most common break is a form field getting renamed (by you, a plugin update, or a client) without updating the Set node downstream -- symptoms show up as blank CRM records, not an error message, so check your CRM after any form edit.
Webhook URL swapped between test and production. n8n gives you a separate test URL and production URL for Webhook nodes -- it is easy to leave your live form pointed at the test URL, which silently stops working the moment you close the editor tab.
Rate limits on the messaging step. If you batch-import old leads through the same workflow, a Twilio or email step built for one-at-a-time real-time leads can hit provider rate limits fast -- add a short Wait node before bulk-running historical data through it.
CRM API auth expiring. OAuth-based CRM connections (HubSpot, Salesforce) periodically need re-authorizing in the n8n credentials screen -- if leads stop appearing with no error in the execution log, check the credential status first.

The tools used

This build only requires n8n itself -- no separate form tool, no separate automation platform. If you are choosing between n8n and the alternatives for this specific use case, see my full breakdown in best automation tool for lead generation (n8n vs Zapier vs Make on lead-gen economics specifically) and n8n Cloud vs self-hosted cost if you are trying to decide which billing model fits your lead volume.

FAQ

How do I automate lead generation with n8n?

Build a workflow with a webhook or form trigger to catch the lead, an HTTP Request or CRM node to push the contact into your CRM, and a condition plus messaging node (Twilio, WhatsApp, or email) to fire an instant follow-up. n8n's built-in Form trigger node means you often do not need a separate form tool at all.

Is n8n free for lead generation automation?

Yes if you self-host -- the Community Edition is free open-source software with unlimited workflows and executions, and your only cost is a small VPS around 5 to 6 dollars a month. n8n Cloud starts at 20 dollars a month annually for 2,500 executions, which is plenty for most solo lead-gen setups but can run out fast if your trigger fires on a tight schedule.

What is the fastest way to get a lead-gen workflow running today?

Import a pre-built template from n8n's own template library (search "lead capture" or "form to CRM") instead of building from a blank canvas -- most get you a working skeleton in under 10 minutes, though expect to rewire one or two nodes if the template references an API version that has since changed. The Template availability currently offers no download or email signup.