🗺️Map questions to contact properties
Map each question of a Dapta Form to a HubSpot contact property: use the searchable property picker, let Auto-map fill the obvious matches, add extra keys such as UTMs and hidden fields with Custom fi
Mapping tells HubSpot where each answer belongs. Until a question is mapped, its answer stays in Dapta Forms and never reaches your CRM.
Open your form, click Connect in the top bar, and scroll to the HubSpot card.
Step 1: Find the Map questions section. It lists every question in the form under Your question, with its field key underneath, and a picker under HubSpot property next to each one.
The helper line states the one rule that matters: Send each answer to a HubSpot contact property. One question should map to "email".
Step 2: Click Auto-map to fill the obvious matches in one go.
Auto-map reads your question text and types, in English and in Spanish, and suggests the standard contact properties: an email question to email, a phone question to mobilephone or phone, a website or URL question to website, a company question to company, a job title question to jobtitle, and first and last name to firstname and lastname.
It never overwrites a mapping you already made. When it finds something you get Auto-mapped {n} question(s). Review and save., and when there is nothing left to suggest you get No new matches to suggest.
💡 Tip: Always review what Auto-map chose. It is a shortcut for the standard properties, not a replacement for reading the list.
Step 3: Set the rest by hand. Click a picker to open the property list, type in Search… to narrow it down, then click the property you want.
Each entry reads Label (internal_name): the label is what your team sees in HubSpot, the value in brackets is the internal name the API uses. Pick (none) to clear a mapping.
Two details worth knowing:
The same question can feed several properties. Map it once here, and add the extra targets under Custom field mappings in the next step.
If your portal cannot be reached for a moment, the card says HubSpot properties are temporarily unavailable, but you can still type a property name. The mapping still saves.
Step 4: Use Custom field mappings for anything that is not a plain question: UTM parameters, hidden fields, or a key you set through the URL.
Click Add mapping, open the left picker and choose the key:
Form questions
Every question in the form, listed as Question text (field_key). Use this to send one answer to a second property.
System fields
The five captured UTM parameters: utm_source, utm_medium, utm_campaign, utm_term and utm_content. On a form with a scheduler step you also get the booking keys (Booking: full name, Booking: first name, Booking: last name, Booking: phone).
Custom key…
Type any key by hand, for a hidden field or a value you pass in the URL. Back to list returns to the groups.
Then pick the HubSpot property on the right. Remove deletes the row. With no rows the section reads No mappings yet.
💡 Tip: Hidden fields and
?key=valueprefill are explained in Hidden fields & URL prefill. Anything that lands in a form field can be mapped here.
Step 5: Check that one question maps to Email (email). This is the mapping the whole integration depends on.
HubSpot matches a contact by email address: it updates the one it finds, or creates a new one. A submission that carries no address cannot be matched, so the lead is not synced at all. If your form has no email question, the card replaces the mapping sections with This form has no email address to sync.
There is one exception. On a form whose only source of an address is a scheduler step, Calendly supplies the invitee address when someone books, and you should not map anything to email. Doing so raises the alert This mapping stops the sync. See How the sync works & troubleshooting.
What's next
Value maps & static properties: translate answers into the values your picklists expect.
Form elements: UTMs, score, outcome, submitted date: map the metadata Dapta Forms captures on its own.
How the sync works & troubleshooting: the email rule, blocked states and the delivery log.
Last updated