To send website form submissions to a CRM automatically, use one of four methods: embed your CRM's native form, capture your existing form with the CRM's tracking script or plugin, connect the form builder to the CRM through Zapier, Make or a native integration, or post submissions to the CRM's API with a webhook. Then map fields and test.
This guide compares all four, gives you a field-mapping template, and ends with a test runbook so leads never silently disappear.
Key takeaways
- Native CRM forms are the simplest and most reliable. Middleware adds flexibility but also a point of failure.
- Decide your unique identifier (email or mobile) up front to avoid duplicates.
- Always pass the source: page URL and UTM tags travel with the lead or attribution is lost.
- Test with real submissions monthly. Integrations break quietly when someone renames a field.
Why an inbox is not enough
Routing forms to a shared inbox works until three enquiries arrive during a busy day and nobody replies for 48 hours. A CRM gives each lead an owner, a follow-up task and a source, and protects data quality. Salesforce's State of Sales 2026 found 79% of top-performing sales teams prioritise data hygiene, compared with 54% of underperformers. Manual copy-paste from email is one of the fastest ways to lose that hygiene. More on that in our guide to CRM data quality.
4 ways to send form submissions to your CRM
| Method | How it works | Best for | Cost | Main risk |
|---|---|---|---|---|
| 1. Native CRM form | Build the form in the CRM and embed it | New forms, non-technical teams | Usually included in CRM plan | Less design control |
| 2. Tracking script or plugin | CRM script or WordPress plugin captures an existing form | Keeping current forms | Often free | Some form types are not supported |
| 3. Native integration or middleware | Form builder connects to CRM directly or via Zapier or Make | Popular builders like Typeform or Tally | Free to paid, depending on tool | Task limits, connector breakage |
| 4. Webhook or API | Form posts JSON to CRM endpoint | Custom sites, developers | Developer time | Needs error handling |
Method 1: Use your CRM's native form
Build the form in the CRM, copy the embed code and paste it on your page. Submissions create contacts automatically. This is the most reliable option because there is nothing in between to break.
Method 2: Capture an existing form with a script or plugin
Some CRMs can read submissions from forms you already have. HubSpot's non-HubSpot forms feature is a well-documented example. It relies on the tracking code loading, requires an email field and a standard submit button, and does not support forms in iframes, single-page apps or forms loaded after the page. Check your CRM's equivalent limits before relying on it.
Method 3: Native integrations or Zapier and Make
Many form builders connect to CRMs directly. If yours does not, middleware links the two: "new form submission" triggers "create or update CRM contact". Watch the plan limits. As of September 2026, Zapier's pricing page lists a free plan with 100 tasks a month and two-step Zaps, with the Professional plan from $19.99 a month. Also note that Webhooks by Zapier is a premium app.
WordPress users should check plugin tiers too. The free WPForms Lite plugin has more than five million active installs, but its CRM integrations are paid add-ons. For a comparison of which free builders include CRM connections, see our roundup of the best free form builders.
Method 4: Webhooks and the CRM API
If you have a custom site or developer help, the form's backend can send a POST request to your CRM's API. This gives full control over validation and routing. Build in retries and an alert if the CRM returns an error, or you will lose leads silently.
How to set it up in 6 steps
- Choose your unique identifier. Email for B2B, mobile number for most Indian B2C businesses. Set the integration to "create or update" on that field.
- Map every field. Use a table like the one below.
- Add hidden source fields. Pass page URL, UTM source, medium and campaign so you can track leads from every channel.
- Set assignment rules. Route by city, product or round-robin so every lead has an owner.
- Trigger the first response. Send an instant email or WhatsApp confirmation and create a follow-up task. Our guide on automating lead follow-up covers sequences.
- Test end to end with the runbook further down.
Field-mapping template
| Form field | CRM property | Format rule | Notes |
|---|---|---|---|
| Full name | First name + last name | Split on first space | Keep original in a note |
| Mobile | Phone | Add +91 or country code, strip spaces | Unique ID for B2C |
| Lowercase | Unique ID for B2B | ||
| Service interested in | Product interest | Drop-down values match CRM list | Mismatches create blank fields |
| utm_source, utm_campaign | Lead source, campaign | Pass as-is | Required for attribution |
| Consent checkbox | Marketing consent | Yes/No with timestamp | Needed for DPDP and GDPR records |
A worked example
Take an illustrative coaching institute in Kota whose enquiries landed in Gmail and were copied into a spreadsheet each evening. With the CRM's WordPress plugin, each enquiry now creates a lead tagged with course and campaign, is assigned to a counsellor, and triggers a WhatsApp confirmation within a minute. Its Facebook ads connect separately; see connecting Facebook Lead Ads to your CRM.
Test runbook: make sure no lead goes missing
- Submit a test lead from each form, with UTM tags in the URL. Confirm the record appears, correctly mapped and assigned, within a minute.
- Submit the same email or number twice. Confirm it updates, not duplicates.
- Break it on purpose. Leave a required field blank and check the error message and the connector log.
- Check after every website change. Theme updates and renamed fields are the most common causes of broken syncs.
- Set a daily alert if zero form leads arrive on a normal business day.
In an agentic CRM such as Autometa CRM, an AI agent can also watch for drops in form volume, flag unmapped fields and draft the first reply for each new lead.
To send form submissions to your CRM reliably, implement direct webhook endpoints with asynchronous retry queues. Avoid relying on simple email notifications that require manual copy-pasting into database fields. Direct API integration guarantees that custom field mapping, UTM attribution parameters, and consent records are accurately preserved inside the contact timeline.
Frequently asked questions
What is the easiest way to send form submissions to a CRM?
The easiest route is to build the form inside your CRM and embed it on your website. Submissions create or update contacts automatically, with no connector to maintain. If you must keep an existing form, check whether your form builder has a native integration with your CRM before reaching for a middleware tool like Zapier or Make.
Can I connect a WordPress contact form to my CRM for free?
Sometimes. Many CRMs offer a free WordPress plugin that captures submissions from popular form plugins or provides its own form. Free versions of form plugins often reserve CRM add-ons for paid tiers, as WPForms Lite does. A webhook from a free form builder into your CRM's API is another no-cost option if you have technical help.
Why are my form leads not showing up in my CRM?
Common causes are a changed field name that breaks the mapping, a required CRM field the form does not send, an expired API key or connector login, a spam filter blocking the request, or a form loaded in an iframe that the tracking script cannot see. Check your connector's error log first, then submit a test lead.
How do I avoid duplicate contacts when syncing forms to a CRM?
Use a unique identifier, usually email or mobile number, and set the integration to update existing records instead of always creating new ones. Normalise phone numbers to one format, such as including the +91 country code, before matching. Most CRMs also offer duplicate rules or merge tools for anything that slips through.
Conclusion: fewer hops, fewer lost leads
The fewer tools between your form and your CRM, the fewer places a lead can disappear. Start with a native CRM form if you can, use plugins or middleware when you must keep an existing form, and reserve webhooks for custom builds. Map fields carefully, pass the source and test monthly.
Want website leads to land in your CRM with an owner and a first reply ready? Try Autometa CRM free.
Related reading
- What Is a Lead Capture Form? Examples and Best Practices
- How to Create a Lead Capture Form That Converts
- Form Conversion Rate Benchmarks and 10 Ways to Improve Yours
- How to Capture Leads From Your Website Automatically
Sources
- Use non-HubSpot forms — HubSpot Knowledge Base, 2026
- Zapier Pricing — Zapier, 2026
- Webhooks by Zapier Integrations — Zapier, 2026
- WPForms Lite plugin — WordPress.org, 2026
- Salesforce State of Sales 2026 — Salesforce, 2026


