Website form leads, scored and answered with a reply I approve
Lead to reply is a system I built to follow up on website form leads. It checks each submission, catches repeats, adds the lead to HubSpot, then scores it and drafts a reply. I approve the draft in Telegram, and Gmail sends it while HubSpot gets a follow up task. It has run end to end on my own accounts.
Form leads that wait, or land in the CRM twice
A lead fills in the form on the website, and the message sits until someone has time for it. Leads that wait for a reply often go somewhere else. When someone does get to it, the details get typed into the CRM by hand. Some leads never make it in, and others show up twice.
I built lead to reply so each form lead lands in HubSpot once, with a score and a drafted reply waiting for me. I read the draft on my phone in Telegram, and I approve every reply.
What is proven and what is not yet
| What it does | Status | How I know |
|---|---|---|
| Runs end to end on the real services | Proven | A test lead passed the checks, went into HubSpot, then was scored with a drafted reply. I approved it in Telegram, Gmail sent the reply and HubSpot got the follow up task. The run left one row in the run log and one record in Langfuse. |
| Scores the lead and drafts a reply | Proven | On one test lead it took 5.35 s from the form to a score and a drafted reply. |
| A declined draft sends nothing | Proven | I declined a draft on the live system. No email went out and no HubSpot task was created. The run log recorded the decline. |
| The same submission sent again does nothing new | Proven | I sent one submission a second time. The run log marked it as a repeat, and it never reached HubSpot, the AI step or Gmail. |
| A failed step reaches me | Proven | A real Gmail sign in failure stopped one send. The run was logged, I got a Telegram alert with how to rerun the lead, and no HubSpot task was created for it. |
| Skips a lead who opted out of email | Not yet proven | The step is built. No opted-out lead has gone through it, in a test or on the live system. |
| An approval nobody answers | Not yet proven | The card waits for my answer. In the only live test of that wait, the lead was dropped with no record and no alert. The fix is not done yet. |
| Turning away an incomplete submission with a clear error | Not yet proven | The clear error back to the form is fixed in the version I'd hand over. That fix has not been run yet. |
| A morning list of untouched leads in Telegram | Not yet proven | The scan that finds them has run on the live system. Posting that list to Telegram has no recorded run yet. |
| The backup alert for failures the main flow can't catch | Not yet proven | A second workflow is set up to catch those. It has never fired for this system. |
| HubSpot limiting how fast it accepts requests | Not yet proven | I tested the failure path with a forced HubSpot failure. A real HubSpot limit has not come up on a live run. |
What you get at handover
- It runs in an n8n account you own, signed in to your own HubSpot, Gmail, Telegram, AI model, Langfuse and Google Sheet.
- Your leads stay in your HubSpot, and the run log stays in a sheet you own.
- A setup guide that walks through connecting each account and sending a first test lead, so the system can be rebuilt from it.
- A plain step by step guide to what each part does, for the person who runs it.
- How failures reach you: a failed step is logged and sent to Telegram with how to rerun the lead. An approval nobody answers is not covered yet.
All of its parts exist in full. The label itself says nothing about live runs.
The logic ran on sample data, with stand-ins for the outside services.
Every outside service it uses was exercised for real on test accounts I own, including failures and reruns.
Running for a client, on the client's own accounts. Nothing I have built is there yet.
Questions
Does anything send without my approval?
Gmail sends the reply only after someone taps Approve on the card in Telegram. Limiting that to the people you name is built, and I haven't tested it with a second account yet. When I declined a draft on the live system, no email went out and no HubSpot task was created.
What happens to duplicate leads?
A submission sent a second time is marked as a repeat, and nothing new happens. When the same person fills in the form again, HubSpot updates their existing contact instead of adding a second one. The new message still gets its own draft for me to approve.
What if nobody approves the draft?
That case is not handled yet. The card waits for my answer, and in the only live test of that wait the lead was dropped with no record and no alert. Until the fix has been tested, it stays on the not yet proven list.
Can it work with a CRM other than HubSpot?
This version is built and tested with HubSpot. Another CRM means swapping the HubSpot steps and testing them again on real accounts before I call it done.
Have you installed this for a client?
No client runs it yet. It has run on my own accounts with test leads, and every result on this page comes from those runs.
Related
- A drafted reply to each lead, approved from my phone before it sendsAI drafts replies to lead emails that pass a junk screen, from my business facts. Risky asks get flagged, and nothing sends until I approve it on my phone.
- The lead-response bottleneck: how fast to answer a new leadHow fast to answer a new lead, why a slow reply hands the decision to someone else, and a system that drafts from your rules for a person to approve.
- The four places a lead diesLeads drain out of a pipeline in four places: never recorded, never answered, never followed up and never closed out. How to count each one this week.
- How do I stop website form duplicates in HubSpot?Where the handoff from your website form to HubSpot makes duplicates or loses leads, which field is the key, what stays with a person, and what I'd pick.
- Dedupe keyA dedupe key is the field a system uses to decide two records are the same person or company. Which key to pick, an example, and what goes wrong without one.
- Human-in-the-loop approvalWhat human-in-the-loop approval means in an automation, which steps should wait for a person, and how an approval card makes sure an email sends once.
- n8n template library for service businessesEvery workflow template I have ready to show for service businesses, with its stage and how far it has been tested. None is offered as a download yet.