A web form to CRM connection takes what someone types into your website form and creates or updates a contact in your CRM, with the right fields filled, an owner assigned and a confirmation sent, within seconds. Getting it right comes down to four decisions: how the form fields map to CRM fields, how you handle duplicates, what happens when it fails, and who tests it every month.
Three ways to connect a form to a CRM
There are three common routes. Each suits a different set-up.
- The CRM’s own form. Many CRMs let you build a form inside them and embed it on your site. The data goes in directly with no connection to break. The trade-off is that you work within the CRM’s form styling and features.
- A plugin or integration for your form tool. If your site is on WordPress, the form plugin may have a ready-made link to your CRM. It is quick to set up. Check what it can and cannot map, as some handle only simple fields.
- A webhook into an automation tool. The form sends the submission to an automation tool, which cleans it up and sends it to the CRM. This gives you the most control over duplicates, routing and checks. Our guide on what a webhook is explains the idea.
CentriWeb builds websites on WordPress, many client systems on GoHighLevel and most client automations in n8n, so we lean towards those. The same principles apply on any set-up.
Field mapping for web form to CRM
Mapping is the list that says “this form field goes into that CRM field”. It sounds trivial and it causes most of the faults.
| Form field | CRM field | Watch for |
|---|---|---|
| Full name | First name and last name | Single names, double-barrelled names, people who type their name in capitals |
| Typing errors, which cause bounces. Use a format check on the form | ||
| Phone | Mobile or phone | Spaces, brackets, a missing country code. Agree on one stored format |
| Service or enquiry type | A tag or a drop-down field | Free text cannot be filtered later. Use a drop-down on the form |
| Message | Note or custom field | Long messages and special characters |
| Suburb or postcode | Address fields | Needed for routing, so make it required if you route by area |
| Page and campaign | Source fields | Capture where the person came from, so you know which marketing works |
Keep the form short. Each extra question lowers the number of people who finish it. Ask for what you need to reply well and no more.
Create the CRM fields before you build the connection. If the form sends a value into a field that does not exist, it is dropped, often without an error.
Handle duplicates before they happen
People submit twice. They also come back a month later with a new job. If every submission creates a new contact, you end up with three records for one person, each with part of the history.
Decide the rule once:
- Match on email first, and on phone number if the email does not match.
- If a match is found, update that contact, add the new message as a note and flag it as a repeat enquiry for the owner.
- If no match is found, create the contact.
- If the same person submits twice within a few minutes, ignore the second send but keep the message.
Many CRMs have this built into their create-or-update option. If you use an automation tool in the middle, add a search step before the create step. Test with the same email twice, in different capitals, because some systems treat them as different.
What should happen in the first minute
Filing the record is only half the job. The value of a connection is what follows it. A sensible sequence:
- Create or update the contact, with the source and the message.
- Assign an owner, by service, area or a simple rota.
- Create a task for the owner, due within your response target.
- Send the customer a confirmation that says when they will hear back and asks one helpful question.
- Notify the owner by text or email, with the person’s name, number and message in the notification.
This is the same approach as in our guide on how fast to reply to an enquiry, which sets out response targets for small teams.
An example: a renovation business enquiry form
This is an example, not a client. A renovation business has one contact form with name, email, phone, suburb, job type from a drop-down and a message.
- Trigger: the form is submitted.
- Steps: the submission goes to the automation tool, which searches the CRM for the email, then creates or updates the contact. It sets the owner by suburb, adds the job type as a tag, creates a call-back task due in two hours during business hours, and sends a text and an email confirmation. It also emails the whole submission to a shared inbox as a backup.
- Check: every Monday, the office manager compares the number of form submissions in the website’s own log with the number of new contacts from the form in the CRM. The two numbers should match, apart from repeat enquiries. Any gap means a submission failed to arrive.
That weekly count takes two minutes and is the most reliable way to catch a silent fault. It works because it compares the front door with what reached the CRM, rather than trusting that the connection is fine.
Routing the enquiry to the right person
A contact sitting in a general list helps nobody. Decide how each enquiry finds its owner. Route by the form answer where you can: job type, suburb or service. If you cannot, use a rota, and name a person who checks the unassigned list each morning. The routing rule belongs in writing, so that when someone leaves, the new person can see what the system was doing.
Spam, consent and privacy
Forms attract spam. A hidden field that humans do not fill in, a simple question, or a check in the form plugin will stop most of it. Without one, the CRM fills with junk, and automatic replies go to made-up addresses, which can harm your email reputation.
Add a clear tick box if you plan to send marketing as well as reply to the enquiry, and store whether the person agreed and when. Rules on consent and privacy differ by country, so check the regulator’s guidance for yours. Replying to the enquiry someone sent you is a different thing from adding them to a newsletter.
When it fails
The most expensive faults are silent: the form shows “thanks, we’ll be in touch” while nothing arrives in the CRM. Guard against it in two ways.
- A backup copy. Have the form also send a plain email to a monitored inbox. If the CRM connection breaks, the email still arrives.
- An alert. If the connection fails, a named person receives a message that shows the person’s details, so the enquiry can be answered by hand.
Our guide on why automations break covers the usual causes, such as expired connections and changed fields.
Test it each month
On the same day each month, someone submits the real form from a phone and a laptop. Check each of these:
- The contact appears in the CRM within a minute, with every field filled in correctly.
- The source and page are recorded.
- The owner is assigned and received the notification.
- The confirmation arrived, and reads well on a phone.
- Submitting again with the same email updates the record instead of creating a new one.
- The backup email arrived.
Also test after any change to the website, the form or the CRM. A new field or a theme update can break the link without anyone meaning to.
When to build it yourself and when to get help
If you have one form, one CRM and a built-in link that maps the fields you need, set it up yourself. It is an afternoon’s work, and you only need to test it. Help is worth considering when you have several forms and services that route to different people, when you need duplicate handling and alerts that the built-in link cannot do, or when nobody in the business has the time to look after it. CentriWeb sets up CRM connections and the automation around them, and will tell you if the built-in option is enough.