Start hereintermediate30 min
Auto-Reply to New Leads in Under a Minute (n8n + Claude)
A workflow watches your lead form, creates or updates the contact in your CRM, and immediately sends a friendly reply so the prospect knows they reached a real business. Because first-response speed is one of the biggest predictors of whether a lead converts, replying in under a minute, automatically, beats competitors who answer the next day.
Auto-Reply to New Leads in Under a Minute (n8n + Claude)
A workflow watches your lead form, creates or updates the contact in your CRM, and immediately sends a friendly reply so the prospect knows they reached a real business. Because first-response speed is one of the biggest predictors of whether a lead converts, replying in under a minute, automatically, beats competitors who answer the next day.
Speed is the cheapest edge in sales
Leads go cold fast. The business that replies in a minute almost always beats the one that replies tomorrow — because by tomorrow the prospect has moved on, or messaged a competitor. The fix is a three-step automation: **catch** the form, **log** the lead, **fire** a warm instant reply. We'll build it in [n8n](/tool/n8n/) with a [Claude](/tool/claude/) step so the reply is personal, not canned, and the lead data stays on your own server.
Four beats, all automatic
Picture the loop. Someone submits your lead form. n8n instantly creates or updates the contact in your CRM. Claude reads what they wrote and sends a friendly, tailored reply. Then you follow up personally — already knowing the lead is captured and warm. You go from prospects waiting hours for any sign of life to **every** lead hearing back in seconds, with nothing slipping through the cracks.
What you'll need
Four pieces, set up once: - An **n8n** account — self-hosted (a few dollars a month) or n8n Cloud. - A **Claude** (Anthropic) API key for the personalized reply. - Your **lead form** — a website form, Typeform, Google Forms, anything that can send a webhook. - An email account to send from, such as **Gmail**.
Catch the form with a webhook
Every n8n workflow starts with a **trigger**. Add a **Webhook** node, and n8n hands you a unique URL. Paste that URL into your form's "send to webhook" or notification setting. Now the instant anyone hits **submit**, their answers arrive in n8n as structured data. Hit **Listen for test event** and submit your own form once to watch the fields land — that's the raw material every later step reads from.
Log the lead in your CRM
Add your CRM node and choose a **Create or Update Contact** action. Map the form's email, name, and any fields you collect into the matching CRM properties. The trick that prevents a messy database: **key on email.** When a returning lead fills the form again, the CRM updates their existing record instead of spawning a duplicate — so one person stays one clean entry, no matter how often they reach out.
Let Claude write a personal reply
Here's what lifts this above a generic auto-responder. Add the **Anthropic (Claude)** node and feed it the lead's message, with a prompt like: ``` Write a short, warm reply to a new lead. Thank them, confirm we have their details, and set the expectation that a person follows up within a few hours. Open with one specific line that references what they actually asked about. No hype, no emojis. Sign it from "Priya, Automate Basics". Lead's name: {{ $json.first_name }} What they wrote: {{ $json.message }} ``` Because it responds to *their* words, Claude returns a reply that reads as hand-written.
Send it in seconds
Add a **Gmail** node set to **Send Email**, and map the recipient to the lead's address and the body to Claude's output. That's the payoff: the prospect gets a thoughtful, personal-sounding reply within seconds of clicking submit — while a competitor's form is still sending a templated "we received your message." Send yourself a test lead and read the email as a prospect would, then tune the prompt until it feels genuinely warm.
Flip it to Active
Switch the workflow to **Active** with the toggle in the top corner. From now on it runs forever, day or night, with no one watching. For extra speed on your end, add one more node that posts each new lead to a team **Slack** channel or texts you — so a human can jump in fast while the auto-reply holds the lead's attention.
Make it yours
Once the core loop runs, layer on the high-value extras: - **Smart routing:** add an **IF** node that assigns the contact to a specific salesperson based on the form's product or region field. - **Lead scoring:** set a CRM property from the form answers so hot leads are flagged the moment they arrive. - **Native fallback:** if all your forms already live in your CRM, the instant reply can often run inside the CRM's own automation — no separate tool needed. A note on tools: hosted builders like Zapier (with a CRM such as HubSpot) can wire up the same three steps. We build it in n8n + Claude here because you keep full control of the data and get a genuinely personalized reply rather than a fixed template.
Your first step
Add a single **Webhook** node in n8n, copy its test URL into your lead form, and submit one fake lead. Watching the real form fields appear in n8n proves the hardest part, the connection, works. Logging, writing, and sending all build on top of that one event.
Try this now
Your turn: open n8n and set up the first step. Just do step one now — the rest takes minutes. Save this guide to pick up where you left off.
FAQ
Does the instant reply have to feel robotic?
No — and with Claude in the loop it really won’t. Thank them, confirm you got their details, set a clear expectation for the real follow-up, and sign it from a person. Claude can read what they actually asked and open with a tailored line, so it reads as personal, not automated.
Why does response speed matter so much?
Because attention fades fast. A lead who hears back within a minute is far more likely to engage than one who waits hours — by which point they’ve often messaged a competitor too. The auto-reply buys you that crucial first moment while you prepare a proper response.
Do I need to pay for hosting?
Self-hosted n8n runs on a small server for a few dollars a month with unlimited runs. n8n Cloud is a hosted option if you’d rather not run a server. The Claude API charges a fraction of a cent per reply. For lead speed, both are easily worth it.
Will it create duplicate contacts?
Not if your CRM node uses a "create or update" action keyed on email. The CRM matches the existing contact and updates it instead of making a second record, so a returning lead stays as one clean entry.