Automating lead follow-up: website form to CRM to email

1. Catch the submission. The form (or a webhook from it) starts the run. Keep the submission's own ID so a retry cannot create a second lead.
2. Clean the input. Trim and lower-case the email; drop empty or obviously invalid submissions before they reach the CRM.
3. Find or create one contact. Look the person up by email; update if found, create if not. One person must never become two records.
4. Create the follow-up. A deal or a task with a named owner and a due date, linked to the contact. Without an owner the automation only moves the pile.
5. Send the first reply. A plain acknowledgement from a real mailbox. Start a longer sequence only if the person agreed to receive one (see the consent section).
6. Stop when the conversation starts. A reply, a booked call, a deal moving to a later stage, an unsubscribe or a bounce each end the sequence. Notify the owner.

Steps 3 and 6 are where most of the value is: step 3 prevents duplicates and step 6 prevents the embarrassing follow-up that arrives after the deal was already won.

The usual key is the email address. What each system does with it is not the same.

What follows from the table. A native create-or-update operation exists for HubSpot on all three platforms and for ActiveCampaign on Zapier and Make. Where only separate create and search operations exist (Pipedrive on Make and n8n), build the find-then-create branch yourself and test it with the same email twice. On n8n, a HubSpot form-submission trigger is not listed in the documentation read for this guide; a webhook from the form is the way in.

HubSpot's documentation lists a contact replying to a sequence email, and booking a meeting through a meetings link, among the events that unenrol the contact from a sequence. HubSpot's article says the reply and meeting events can be switched off in the sequence's Automate tab, so check those switches. Pipedrive's help page on automated campaigns says they require the Campaigns add-on and lists the plans that can use it; Pipedrive's plan names differ between its help pages and its pricing page, so check eligibility on the live pricing page. The stop rules for ActiveCampaign automations were not confirmed for this guide.

Whatever the tool, write the stop rule down and test it: send yourself a lead, reply to the first email, and check that no second email arrives. Test a bounce and an unsubscribe the same way. A sequence that cannot be stopped from the CRM should not be started from it.

Replying to someone who wrote to you is not the same as adding them to a marketing sequence. Keep the first reply to the enquiry itself, and start a longer sequence only where the person agreed to it or where you have checked that the rules in your market allow it. What the regulators' own pages say:

• UK. The ICO says the electronic-mail marketing rule does not apply to corporate subscribers, but that sole traders and some partnerships are individual subscribers who must be given the chance to opt out. The ICO states this guidance is under review. It also says the right to object to direct marketing is absolute.
• EU. The EDPB's guide for small businesses says an objection to direct marketing must lead to the immediate end of that processing.
• US. The FTC's CAN-SPAM guide says an opt-out request must be honoured within 10 business days, that a message must include a valid physical postal address, and that the law makes no exception for business-to-business email.

Practical rules that follow, which are editorial advice rather than a legal reading: record where and when each person agreed; make the unsubscribe work in the CRM and in the automation tool at the same time; never email a person who has objected; and take legal advice for your own markets, because EU member-state rules for business email were not reviewed here.

The workflow: an instant (webhook) trigger, then five steps (clean and check, find or create the contact, create the deal or task, send the first email, notify the owner). Each run is one lead. Counted in each platform's own unit: Make counts a credit for each module run and, as the calculator assumes, one for the instant trigger; Zapier counts each successful action as a task and does not charge for the trigger or for Filter, Paths, Formatter and Delay steps (the table assumes five counted tasks per lead; if the cleaning step is a Formatter or Filter step it is four, and the plan is the same at both counts); n8n counts one execution per whole run. The calculator and the two guides on pricing units and one worked workload explain the rules and their caveats. Open this workflow in the calculator: 200 leads a month or 1,000 leads a month.

The count is small enough that each platform's smaller published plans cover it, and the prices differ because the plan sizes and the unit rules differ. The input that changes the answer most is the trigger. If your form tool cannot send a webhook and the platform has to poll for new submissions every 5 minutes, Make's help page counts each check of a polling trigger as one operation (its example says one per check; it does not say what happens when a check finds nothing, and the calculator assumes a credit per check): on that assumption the 200-lead workflow becomes 9,640 credits a month on Make (Core, $9/mo), against 1,200 with an instant trigger. Zapier does not charge tasks for polling, and on n8n a polling trigger counts only when it finds new data (a schedule trigger counts every firing).

• Your form can send a webhook and volume is small. All three have a published plan that covers it (see the table), so the decision rests on the CRM connection and on who maintains the workflow.
• You use HubSpot or ActiveCampaign and want the least custom work. Zapier and Make list a native create-or-update contact operation for both; n8n lists it for HubSpot but no automation operation for ActiveCampaign.
• You use Pipedrive. Zapier lists a find-or-create person action; on Make and n8n you build the find-then-create branch.
• You must poll rather than receive a webhook. Price the polling on Make before you choose; see the paragraph above.

Whoever will own the workflow should choose among the options that fit: pick the tool that person can read and fix, not the cheapest line in a table.

All three routes work, and the guide above gives the facts for each connector. The sections above are enough to build any of them yourself.

• Submit the same email twice, once in capitals: one contact must result.
• Submit an empty email and a malformed one: nothing must reach the CRM.
• Turn the CRM off for a minute: the run must fail visibly and tell a person, not vanish.
• Reply to the first email: the sequence must stop.
• Unsubscribe: the person must be suppressed in both the CRM and the automation tool.
• Check the owner and due date on the created deal or task.
• Write down who owns the workflow, and what they do when it fails.

• Testing. No platform or CRM was used for this guide.
• Email deliverability. Sender reputation, authentication and content are outside it.
• CRM seat prices. See choosing a CRM for a small B2B service business.
• Legal advice. The regulator pages above are pointers, not a reading of your obligations.
• Tax and regional prices. None of the pricing pages states how tax is treated.