Disclosure: This post contains affiliate links. If you sign up or buy through them, we may earn a commission at no extra cost to you.
In short5 min read
- Trigger the workflow from a form webhook so each lead is handled the moment it arrives.
- Log and de-duplicate leads in your CRM before any email is drafted.
- Add a one-click approval step so no AI draft reaches a lead unchecked.
- Every scheduled follow-up should first check whether the lead already replied.
The quickest way to automate lead follow-up is a single workflow: a form sends each new lead to n8n or Make, the workflow logs it in your CRM, drafts a reply, waits for your one-click approval, sends it, and schedules follow-ups that stop as soon as the lead answers. Either tool can run it. Keep a human approval step before the first email until you trust your drafts.
This guide walks through the build in tool-neutral steps and notes where n8n and Make differ. If you have not picked a tool yet, our n8n vs Make vs Zapier comparison covers pricing and fit, so this page does not repeat it.
In this article
What a good lead follow-up workflow does
Most solo businesses do not lose leads because their offer is weak. They lose them because the reply goes out late, the follow-up never happens, or a lead falls through the cracks between an inbox and a spreadsheet. Automation fixes the mechanics, not the message.
A reliable workflow does five jobs:
- Capture every submission the moment it arrives.
- Record the lead once, in one place, with its source.
- Draft a first reply that uses what the lead wrote.
- Gate that reply behind your approval.
- Follow up on a schedule, and stop when the lead responds.

The one difference that matters for this build
For lead follow-up, the deciding difference between the two tools is not price. It is how each one pauses for your approval.
n8n can pause inside a single workflow. Its Wait node can resume on a webhook call, using a resume URL that is unique to each execution, or on a form submission, and you can set a limit so a run does not wait forever. Make splits the same job across two scenarios: one drafts and stores the reply, and a second one, triggered by an approval link, sends it.
Both work. If you like seeing the whole flow in one place, n8n’s single-workflow pause is simpler to follow. If you prefer a visual builder and already know Make, the two-scenario pattern is easy to maintain.
The 6-step build
Step 1: Send form submissions to a webhook
Create a webhook in your tool and point your website form at its URL. If you are going with Make, you can start with Make's free plan and build this whole workflow there.
Make’s webhook documentation says custom webhooks run the scenario as soon as a request arrives, and that scenarios with instant webhooks run in parallel by default. If order matters, turn on the Process data in order setting so each run waits for the previous one. One more detail: Make deactivates webhooks that are not connected to any scenario for more than 5 days, so keep your test webhook attached.
Step 2: Clean and de-duplicate the lead
Before anything else, normalize the email address (trim spaces, lowercase it) and search your CRM for an existing contact. If the person already exists, update the record instead of creating a duplicate and skip the welcome sequence.
This single check prevents the most common embarrassment: a returning customer getting a new-lead email.
Step 3: Log the lead in your CRM
Create or update the contact with the form fields, the page they came from and a status such as New. If you do not have a CRM yet, a spreadsheet with one row per lead works as a start. What matters is that the workflow, not you, writes the record.
Step 4: Draft the first reply
Use a template with merge fields, or an AI step that drafts a reply from the lead’s message. Give the AI step strict instructions: short, specific to what they asked, one clear next step, no promises about price or timing you have not approved.
Step 5: Add the human approval step
This is the step most tutorials skip, and the one that protects your reputation.
- In n8n: after the draft, send yourself the draft by email or Slack with the Wait node’s resume URL, then let the Wait node hold the run until you click. If your draft comes from an AI Agent that uses tools, n8n also supports human review before an AI tool runs, with approval channels that include Slack, Gmail, Telegram and Microsoft Teams.
- In Make: store the draft and lead ID, for example in a data store or your CRM, and email yourself an approval link that points to a second scenario’s webhook. When you click it, the second scenario sends the email and updates the CRM status.
Step 6: Schedule follow-ups that know when to stop
Save a next follow-up date on the lead record. Run a scheduled workflow once or twice a day that finds leads due for a follow-up, checks whether they replied or booked, and only then sends the next message. Mark a lead Closed after your last planned touch so it leaves the sequence.
Before going live, push three fake leads through: a normal one, a duplicate, and one that replies after the first email. If all three end in the right CRM status, you are ready.
When to remove the approval step
Approval costs you a few seconds per lead, which is cheap while volume is low. Consider removing it for a specific template only after you have approved a long run of drafts without editing them. Keep it for high-value leads, unusual requests and anything mentioning price.
If you later offer this setup to clients, the selling AI automation services hub covers how to package it. For more n8n builds, see the n8n automation hub.
Mistakes that quietly break lead follow-up
The workflow above is simple. What breaks it is usually small, and usually silent.
| Mistake | What happens | Prevention |
|---|---|---|
| No reply check | A lead who already answered gets a chasing email | Check CRM status or inbox before every follow-up |
| Duplicate contacts | Same person gets two sequences | Search by normalized email before creating |
| Unapproved AI drafts | Wrong price or tone reaches a prospect | Keep the approval gate until drafts are consistently right |
| No error alert | Leads stop flowing and nobody notices | Send yourself an alert when a run errors |
| Wrong time zone | Follow-ups go out at odd hours | n8n’s Wait node docs say “At specified time” always uses server time, so set your server’s time zone or use relative waits |
| Detached test webhook | A Make test webhook stops responding | Keep every webhook attached to a scenario |
The common thread: each of these fails without an error message a lead would ever see. A short weekly look at your CRM statuses catches most of them before they cost you a deal.
Sources: docs.n8n.io (Wait node and human-in-the-loop for AI tools) and help.make.com/webhooks, checked November 2026.
Map your path from form to first reply today
Draw your current path from form to first reply on paper and mark every manual step. Then build steps 1 to 3 of this guide so every new lead lands in your CRM automatically.
Get new AI automation playbooks by email
One email when new guides and case studies go up. No spam, unsubscribe anytime.

Leave a Reply