🟠HubSpot
Send every Dapta Forms submission to HubSpot as a contact. Learn what the integration syncs, how contacts are matched by email address, what reaches HubSpot on a partial submission versus a completed
The HubSpot card turns each submission into a contact in your portal. Answers become contact properties, UTMs and lead score can be stamped alongside them, and completed submissions can add a note and a form submission activity.
Connect HubSpot once for the whole account from Integrations in the left rail (see Connections (account level)), then map fields form by form from the Connect tab.
What the integration syncs
Dapta Forms writes to contacts only. There are no deals, companies or tickets: the company and website properties can be filled from the email domain, but nothing else is created.
Every submission is matched to a contact by email address. HubSpot updates the contact it finds, and creates a new one when there is no match. That single rule explains most of what follows: a form that never collects an email address has nothing to identify the person with, so nothing is synced.
HubSpot connected badge
Your account already has a HubSpot connection, so you can pick real properties from the pickers. Without it the card shows Connect HubSpot to map this form and a Go to Connections button.
Enabled / Disabled switch
Turns the whole destination on or off for this form. Switching it off stops new deliveries and keeps every mapping you configured.
How the sync works
The short explainer above the mapping sections. See How the sync works & troubleshooting.
⚠️ Note: The Connect tab has no Save button, and integration changes are not part of your draft. The footer reads Changes saved automatically, and what you change on the HubSpot card applies to the live form right away, without clicking Publish.
Partial and complete submissions
A form can save answers twice: once at the partial submit point (as soon as the email address is known) and once when the respondent reaches the end. HubSpot receives both, but they do not carry the same payload.
Sent on a partial submission
Sent only on a complete submission
The contact upsert (create or update, keyed on email)
The score in the Score property
Every answer mapped under Map questions
The heading of the matching outcome in the Outcome property
Every Custom field mapping, including UTMs
Every entry under Static properties
The UTM mappings under Map form elements
The note from Create a note on completed submissions
Value translations applied to those answers
The activity from Record a form submission in HubSpot
That split is deliberate: a lead who abandons halfway still lands in your CRM with a name and an email, and the qualification data is added later if the person finishes.
Where each setting lives
All of it sits inside one card, in this order.
Map questions to contact properties: send each answer to a contact property, use Auto-map for the obvious ones, and add extra keys such as UTMs or hidden fields under Custom field mappings.
Value maps & static properties: rewrite answers into the exact values your HubSpot picklists expect, and stamp fixed values on every completed submission.
Form elements: UTMs, score, outcome, submitted date: the Map form elements section plus the Infer company from email, Create a note on completed submissions and Record a form submission in HubSpot switches.
Booking sync: the contact properties stamped when someone books a meeting from a scheduler step.
How the sync works & troubleshooting: the email rule, the states that block the sync, and how to read the HubSpot history log.
What's next
Connections (account level): connect HubSpot to your account before mapping anything.
Scheduler step & Calendly: let respondents book a meeting inside the form.
Webhooks: send the same submission to your own endpoint as JSON.
Delivery, retries & history: what happens after a submission, and how retries work.
Last updated