n8n Lead Capture Workflow: Form to CRM in 30 Minutes
A ready-to-import n8n workflow that captures form submissions, deduplicates them, and pushes clean leads into your CRM and Slack.
No-Code & AutomationPDF · 6 pages· v1.0
4.6A ready-to-import n8n workflow that captures form submissions, deduplicates them, and pushes clean leads into your CRM and Slack.
No-Code & AutomationPDF · 6 pages· v1.0
4.6This guide hands you a complete, self-hosted n8n workflow that turns any web form into an automated lead pipeline. When a lead submits, the workflow validates the email, normalizes the data, checks for duplicates, creates or updates a contact in your CRM (HubSpot or Pipedrive), and posts a formatted notification to a Slack channel so your sales team responds within minutes. It is written for founders, marketers, and operations people who run n8n (cloud or self-hosted) and are tired of copy-pasting leads between tools. You do not need to be a developer, but you should be comfortable opening the n8n editor and pasting API keys into credential fields. After following this guide you will have a working webhook endpoint you can point any form at (Typeform, Webflow, a plain HTML form, Tally), reliable deduplication so the same person never creates two records, and an audit trail of every lead. The guide explains every node so you can adapt it instead of treating it as a black box. Everything uses real, documented n8n nodes and standard REST APIs. There are no third-party paid add-ons required beyond the tools you already pay for.
Either works. The workflow uses only core and built-in app nodes that exist in both n8n Cloud and self-hosted Community edition. Webhook URLs differ slightly between the two, which the guide explains.
HubSpot and Pipedrive are covered in full with exact node settings. The deduplicate-then-upsert pattern is generic, so the guide also shows how to swap in any CRM that has a search and a create endpoint.
No. The workflow searches your CRM by email before writing. If a match exists it updates that record; otherwise it creates a new one. This is the core reason the workflow exists.
The Set node in step 3 is where you map incoming fields to canonical names. The guide shows exactly how to remap so the rest of the workflow stays unchanged.
Read the full refund policy and trust & safety terms.