Send form submissions to HubSpot
Create or update contacts by email, map UTM fields and use the complete server-side relay example.
Follow the HubSpot CRM tutorialWeb form to CRM · support checked November 2026
Send website form submissions to your CRM.
To send website form submissions to a CRM, point your existing form at splitforms, then send its signed webhook to Zapier, Make, n8n or a small server-side relay that calls your CRM's API. splitforms does not currently offer a one-click native HubSpot, Pipedrive or Salesforce connector.
Which HubSpot, Pipedrive and Salesforce routes are supported?
Every route below uses the existing splitforms outbound webhook. Choose an automation tool for a no-code workflow, or use a server-side relay when you need direct control over API calls, duplicate handling and field mapping.
| CRM | Native connector | Supported routes | Typical CRM record |
|---|---|---|---|
| HubSpot | No one-click connector | Zapier, Make, n8n or signed webhook + API relay | Contact (with optional deal or company association) |
| Pipedrive | No one-click connector | Zapier, Make, n8n or signed webhook + API relay | Person plus a Lead or Deal |
| Salesforce | No one-click connector | Zapier, Make, n8n or signed webhook + API relay | Lead |
How do you connect a web form to your CRM?
1. Point your existing form at splitforms
Create a form in splitforms and copy its access key into your HTML form. Keep your current design and field names; submissions are stored, spam-filtered and emailed before any CRM routing. The form-to-webhook setup guide shows the form markup.
2. Choose how the webhook reaches the CRM
Pick Zapier for guided no-code automation, Make for visual scenarios and branching, or n8n for cloud or self-hosted workflows. For direct API control, follow one of the CRM relay tutorials below instead.
3. Add the destination webhook URL
Create a webhook trigger in your chosen automation tool, or deploy your API relay. Copy its URL into the form's Webhooks tab in splitforms. Outbound webhooks are available on paid plans; compare splitforms plans and your automation provider's pricing separately.
4. Map form fields and add the CRM action
Map name, email, phone, company, message and any campaign fields to the CRM record. Keep API credentials in the automation tool or relay, never in browser code. The detailed platform instructions are in the Zapier, Make and n8n setup guides.
5. Submit a test and check both systems
Send one test entry, confirm the expected contact, lead or deal appears in the CRM, and check splitforms' webhook delivery log. Then activate the automation workflow if it is not already live.
Which CRM connection route should you choose?
- Zapier: choose this for the most guided no-code setup and a simple webhook-to-CRM action.
- Make: choose this when you want visual routing, filters or several actions after each submission.
- n8n: choose this when you want a cloud or self-hosted workflow and control over where automation runs.
- Signed webhook + API relay: choose this when you need custom duplicate handling, exact payloads or direct control of CRM API requests.
Whichever route you choose, keep the original submission in splitforms as an independent record and email notification. A CRM or automation outage then does not erase the lead.
Where are the detailed form-to-CRM tutorials?
Send form submissions to Pipedrive
Find or create a Person, attach a Lead and keep your Pipedrive API token off the public website.
Follow the Pipedrive CRM tutorialSend form submissions to Salesforce
Create Leads through the REST API, map standard fields and handle duplicate submissions.
Follow the Salesforce CRM tutorialHubSpot also has a dedicated HubSpot form integration entry covering its webhook relay and Zapier or Make routes.
Form-to-CRM frequently asked questions
Does splitforms have a native HubSpot, Pipedrive or Salesforce integration?
Not a one-click native connector today. All three CRMs work through a splitforms signed webhook sent to Zapier, Make or n8n, or to a small server-side relay that calls the CRM API. The HubSpot integration entry and the three CRM tutorials on this page document these existing routes.
What is the easiest way to send web form submissions to a CRM without code?
Use Zapier for a guided setup, Make for more visual branching, or n8n if you want a cloud or self-hosted workflow. In each tool, start with its webhook trigger, add the CRM action, paste the generated webhook URL into splitforms and map the form fields to CRM fields.
Can I keep my existing HTML, React or Next.js form?
Yes. Keep your form design and fields, set its action to https://splitforms.com/api/submit with method POST, and add your splitforms access key. CRM routing happens after splitforms receives the submission, so you do not need to embed a CRM-hosted form or its JavaScript.
Should my browser call the CRM API directly?
No. CRM access tokens and other credentials must stay server-side. Let splitforms send the submission to your automation tool or to a small server-side relay, and keep the CRM credential there. Visitors only see the public splitforms access key, never the CRM secret.
Can I send form submissions to a CRM on the Free plan?
CRM delivery uses outbound webhooks, which are included on paid plans starting with Pro at $5 per month. The Free plan still stores 500 submissions in total and sends email notifications, so you can build and test the form before enabling CRM delivery. Automation services may charge separately.
What happens if the CRM route fails?
The submission is still stored in the splitforms dashboard and sent by email. Webhook delivery has an 8-second timeout and one automatic retry after about 2 seconds for network errors, timeouts and 5xx responses; 4xx responses are not retried. The delivery log records the result so you can fix and replay a failed delivery.
Keep your form. Send every lead to your CRM.
Create your form and test it with 500 free submissions in total. Upgrade to Pro when you are ready to enable signed webhook delivery to your CRM route.
Get your free access key →