How to build a lead capture flow that writes every website enquiry into your CRM
Short answer: A lead capture flow is the chain of steps between a visitor pressing Submit on your website form and a named person seeing that lead inside your CRM (customer relationship management software, the tool that stores your contacts and deals). A sound flow has six links: a short form, a spam check, a connection that sends the data, a duplicate rule, a record written to the CRM, and an alert to one person. Build all six, then test each one, because a flow that fails quietly loses leads you paid to attract.
You have a website form and a CRM, and you want every enquiry to land in the CRM without someone copying it over by hand.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The shortest answer: do not just point a form at a CRM and hope. Treat it as a small production line with six links, give each link an owner, and test each one on purpose. Most lost leads come from one weak link, not from the whole system being bad. This page shows the links in order, which connection method to choose, what each of three common CRMs (HubSpot, Salesforce and Pipedrive) does when a form arrives, and a test plan you can run in an afternoon.
It is written for owners of service businesses, agencies and small sales teams with a website, a CRM and fewer than a few hundred enquiries a month. If you only need the basics of wiring a form to a CRM, start with connecting HubSpot, Salesforce or Pipedrive to your website. If your forms already fail, go to the forms-not-sending checklist. This page is about designing the whole flow so it does not fail in the first place.
The flow in one table
| Link | What happens | Who owns it | What usually breaks |
|---|---|---|---|
| 1. Form | Visitor fills a short form | Marketing or the site owner | Too many fields, no email field, form inside an iframe |
| 2. Spam check | Bots are blocked before they reach the CRM | Site owner | Check done in the browser only, so bots skip it |
| 3. Connection | Data moves from the site to the CRM | Whoever built it | Silent failure, expired login, rate limit |
| 4. Duplicate rule | Existing contacts are matched, not copied | CRM admin | Same person created twice, or a rule that blocks the form |
| 5. Record and owner | Lead is created and assigned to a person | Sales lead | No default owner, so the lead sits unassigned |
| 6. Alert and reply | A human is told and the visitor gets a message | The assigned person | Alert goes to a shared inbox nobody watches |
Link 1: keep the form short and make email required
Every extra field costs you completed forms. The Nielsen Norman Group (a usability research firm) advises removing fields you can work out yourself, can ask for later, or do not need, and shows an example that went from six fields to two. There is no fixed maximum, so decide by asking what you need to make the first reply.
- Always required: email, because most CRMs use it to recognise the same person twice. Use a real email input type so the browser checks the format.
- Usually required: name, and one question about what they want (a dropdown beats free text).
- Optional, at most one or two: phone, company, budget. Label them optional.
- Hidden fields: the page address the form was on, and the source (for example "google-ads" or "website"). These cost the visitor nothing and tell you later which pages earn leads. One catch: HubSpot's capture of a non-HubSpot form skips hidden fields, so if you rely on it, send the source another way.
Check your CRM's own minimum before you design the form. A Pipedrive lead created through its API needs a title and must be linked to a person or an organization. A HubSpot contact created through its API needs at least one of email, first name or last name. If your form leaves out something the CRM insists on, the record will be rejected and nobody will see an error.
Link 2: stop spam before it reaches the CRM
Spam fills your CRM with junk, wastes the time of whoever reads it, and can eat into limits (more on those below). Use two cheap layers together. The first is a honeypot, a form field hidden from real people that bots fill in, so a filled honeypot means discard. The second is a bot check such as Cloudflare Turnstile, a free CAPTCHA alternative that works on any site.
The detail people miss: the check must be confirmed on a server. Cloudflare's own documentation says tokens can be forged, so showing the widget is not enough. Your server sends the token to Cloudflare's validation address, and a token is single use and valid for 300 seconds. If you use a form tool that does this for you, confirm that it does. The full setup is in how to stop spam on your website contact form.
Link 3: choose how the data reaches the CRM
There are four ways, from least to most effort. Pick the first one that does the job.
| Method | Good when | Watch out for |
|---|---|---|
| The CRM's own form, embedded on your site | You use HubSpot and can embed its form | Styling is limited, and the form must not sit inside something the CRM cannot read |
| Your existing form plus the CRM's capture tool | You already have a form you like | HubSpot lists nine reasons a non-HubSpot form is not captured (see below) |
| A form tool plus an automation tool (Zapier or similar) | You want no code and need a few extra steps | Task limits and monthly cost |
| A small server endpoint that calls the CRM's API | You need exact control, many sources or custom rules | Someone must build and maintain it. Secret keys must never sit in browser code |
HubSpot's nine capture blockers. HubSpot (a CRM and marketing platform) can capture forms it did not build, but only when its tracking code is installed on the page and its non-HubSpot forms setting is on. Its help page then lists nine reasons a submission is still missed: the form is not inside form tags, it sits in an iframe (a page embedded inside another page), JavaScript is bound to the submit button, the form loads after the page finishes, the site is a single-page app, it has sensitive fields such as card numbers, it uses hidden fields, the email field is not a real email input, or the button is not a standard submit button. If your form is custom-built, your developer should read that list first.
Automation tools. Zapier, a tool that moves data between apps, shows a Free plan with 100 tasks a month and two-step flows only, with webhook connections starting on the Pro plan. Webhooks are the messages a form sends to another system when someone submits. As of November 2026 its Pro 750-task plan was listed at $19.99 a month on annual billing and $29.99 monthly. Prices change, so check the vendor page. Tally, a form builder, lists Google Sheets, Notion, Airtable, Zapier, Make (another automation tool) and webhooks as free integrations on its Free plan.
Direct API. HubSpot documents a submit endpoint for forms that needs no login and returns a clear error list. It needs only a list of fields to work, and it takes an optional tracking token (called hutk) that keeps the visitor's page history attached to the contact. Without that token you lose the source information, not the lead. HubSpot's documentation labels this endpoint "legacy", so check what your account recommends today. For anything that needs a secret key, put a small server between the browser and the CRM. If your data goes to a database such as Supabase (a hosted database service), use the pattern in the row-level security fix article.
Link 4: decide what happens when the person already exists
Decide this before you launch, because the CRMs behave differently.
- HubSpot: matches contacts by email. A form submission from an email already on file is added to that contact, not copied. Companies are matched by their primary domain, but companies created through the API are not matched by domain, and imports without a unique identifier create new contacts.
- Pipedrive (a sales CRM built around a deal pipeline): its leads documentation does not describe duplicate handling. Plan to search for the person first, then attach the lead to the match, and remember that search calls cost more of your daily allowance than a plain create.
- Salesforce (a large CRM used by bigger teams): a duplicate rule set to block can reject Web-to-Lead submissions, so the fix is a rule condition that excludes the user the form runs as. Test this before launch.
Whatever CRM you use, the rule should be: same email means same person, so update and add a note, never create a second record.
Link 5: write the record with an owner and a source
A lead with no owner is a lead nobody calls. Set a default owner for web leads in the CRM, or a simple rule such as round robin (take turns between salespeople). For the rule design see lead routing automation for a small team. Every record should carry the source, the page, the date and the visitor's own words from the form. Salesforce Web-to-Lead needs a default lead creator and an assignment rule or default owner to work. Its FAQ states a cap of 500 leads in a 24-hour period, with extra requests going to a pending queue shared with Web-to-Case, up to 50,000 combined, after which new requests are rejected. For most small businesses 500 a day is not a problem, but a spam attack or a big ad day can reach it.
Link 6: alert one named person and reply to the visitor
The flow is not finished when the record exists. It finishes when a person acts. Send an instant alert (text, a Slack chat message or email) to the owner of the lead, not to a shared inbox. Then send the visitor an automatic reply that says what happens next and when, for example "A person will reply by 10am tomorrow."
Speed matters, but be careful with the statistics people quote. The source behind most of them is a Harvard Business Review article, "The Short Life of Online Sales Leads" (Oldroyd, McElheran and Elkington, March 2011), whose teaser says most companies are not responding nearly fast enough. The article itself is behind a paywall, and secondary pages quote different sample sizes and different multipliers, so I do not repeat any single number as the finding. A newer source, a March 2026 vendor study by the automation company Workato, covering 114 business-to-business companies, measured an average first email reply of about 11 hours 54 minutes, and found companies with a lead routing tool averaged about 3 hours 32 minutes against nearly 13 hours without. That is a vendor study of business-to-business demo requests, not of home services, so treat it as a direction, not a promise. The practical takeaway is simple: set your own target, measure it, and make the alert reach a person. See the speed-to-lead system for the reply side.
Know the limits so a busy day does not drop leads
These are published limits as of November 2026. Check the vendor pages for your plan.
| CRM | Limit that matters |
|---|---|
| HubSpot | Private apps on Free and Starter: 100 requests per 10 seconds and 250,000 a day; Professional 190 and 625,000; Enterprise 190 and 1,000,000. Over the limit returns a 429 error. Check each API's guide for batch sizes. |
| Pipedrive | Daily budget of 30,000 base tokens times a plan multiplier (1 on Lite up to 7 on Ultimate) times the number of seats. A search costs 40 tokens; for the cost of creating a lead, check the Pipedrive API reference. Over budget returns 429 until the budget resets at midnight server time. |
| Salesforce | Web-to-Lead: 500 leads per 24 hours, then a queue. |
A 429 error means "too many requests, wait". Your flow should retry after a short pause and put failed items in a list a human checks, rather than dropping them.
A worked example with made-up numbers
These numbers are invented to show the method. A cleaning company gets about 60 website enquiries a month. The old flow: a form emails the office inbox, and the office manager types leads into the CRM when she has time. In a spot check of ten leads she found three that were never entered. Under the new flow: a four-field form (name, email, service, postcode), a honeypot plus Turnstile checked on the server, a Zapier flow that finds the contact by email and either updates it or creates it, a default owner, a text alert to the owner, and an auto-reply promising a call before noon next working day. The running cost is the automation plan plus half an hour to set up. After a month she compares the form log (60) with new CRM records (58, because two were repeat visitors who were updated, not copied). The numbers match, so the flow passes.
Test plan with pass and fail checks
Run these before launch and again after any change to the form, the CRM or the automation.
- Happy path. Submit with a fresh email from a phone on mobile data. Pass: a CRM record appears within two minutes with every field, the source and the right owner. Fail: anything missing or late.
- Duplicate. Submit again with the same email and a different message. Pass: one contact, two activities or notes. Fail: two contacts.
- Missing field. Remove a field your CRM requires, in a test copy. Pass: you see an error in a log you actually check. Fail: silence.
- Spam. Fill the honeypot and submit. Pass: no CRM record. Fail: a record appears.
- Alert. Pass: the named person gets the alert within a minute. Fail: no alert or a wrong recipient.
- Auto-reply. Send to a Gmail address and an address on another domain. Pass: it arrives in the inbox, not spam. Fail: spam folder (see the email-sending notes in the forms-not-sending checklist).
- Outage drill. Turn the connection off and submit. Pass: the submission is stored somewhere you can recover it, and someone is warned. Fail: the lead is gone.
- Monthly audit. Compare form log count with new CRM records. Pass: they match, allowing for repeat contacts. Fail: investigate before more ad money goes in.
Who should skip building their own flow
- If your CRM offers an embeddable form and your site can host it, use that and skip the automation tool.
- If you get fewer than about five enquiries a month, a form that emails you and a calendar reminder to enter them is cheaper than any automation.
- If you have no CRM yet, choose the CRM first. See CRM for small business.
How I'd approach this
Start from the lead, not the tools. Write down the six links with a name next to each, pick the simplest connection method that covers your CRM, and run the test plan before you spend on ads. If I were doing this for a small business, week one would look like this: day one, cut the form to its useful fields and add the hidden source field; day two, set the CRM's default owner and duplicate rule; day three, build the connection and the alert; day four, run all eight tests and fix what fails; day five, switch it live and put the monthly audit in the calendar. When the flow needs more than a form tool and an automation can do, such as several sources, custom rules or a half-built connection that keeps failing, Blur Studio builds the custom version, with CRM and calendar connections and ongoing care. Details are on the business page.
Related guide: connecting a marketing site to your own app or database.
Related guide: turning a website into a quote request tool.
Questions people ask
What is the easiest way to send a website form to a CRM?
Use the CRM's own embeddable form if your site allows it, because there is nothing to connect. If you must keep your current form, use the CRM's capture tool or a form tool with a built-in CRM integration. Reach for an automation tool or code only when those cannot do the job. See connecting a CRM to your website.
Why does my form submit but nothing appears in the CRM?
The usual causes are a missing required field, a duplicate rule that blocks the submission, an expired connection login, a form the CRM cannot read, or a rate limit. First check the form's own log to see whether the submission arrived, then the CRM's error log. The forms-not-sending checklist gives the order to check.
How do I stop duplicate contacts from forms?
Use email as the match key. HubSpot adds a form submission to the existing contact with the same email. In other CRMs search for the email first and update the match. Test with the same email twice before launch.
Do I need Zapier to connect a form to a CRM?
No. Many CRMs have an embeddable form or a capture tool, and many form builders connect directly. Zapier helps when you need extra steps such as an alert, a lookup or two systems. Check the vendor's pricing page, because webhook features can need a paid plan.
How fast should I respond to a website lead?
As fast as you can sustain, and measure it. Research on lead response exists, including a 2011 Harvard Business Review article, but quoted multipliers vary between sources, so set your own target and track your real first-reply time. See the speed-to-lead system.
What are the rate limits I should know about?
As of November 2026: HubSpot private apps on Free and Starter allow 100 requests per 10 seconds and 250,000 a day, Salesforce Web-to-Lead allows 500 leads per 24 hours, and Pipedrive uses a daily token budget. Small businesses rarely reach them, but spam and ad spikes can. Check each vendor's page for your plan.
Is storing form data in a CRM covered by privacy law?
Yes, form data about people is personal data, and rules differ by country and state. Add a clear consent line where your law needs one, store the consent with the record, and collect only what you need. This is information, not legal advice, so check local law. See website visitor tracking and privacy law.
When should I get a custom flow built instead?
When you have several lead sources, rules a form tool cannot express, a flow that keeps failing, or a half-built connection. Blur Studio builds these; see the business page.
More in this topic: Websites: custom builds, portals, lead capture and site care (9 guides) →
Sources
- HubSpot: submit form data API (legacy v3)
- HubSpot: API usage guidelines and rate limits
- HubSpot: non-HubSpot forms FAQ
- HubSpot: deduplication of records
- Salesforce: how many leads Web-to-Lead captures
- Pipedrive: Leads API
- Pipedrive: API rate limiting
- Cloudflare Turnstile: server-side validation
- Nielsen Norman Group: web form design
- Harvard Business Review: The Short Life of Online Sales Leads (March 2011)
- Workato: lead response time study (2026)
- Zapier pricing