HubSpot CRM integration
Connect a HubSpot account with OAuth and automatically create or update Contacts from eligible form submissions.
What the integration does
When you enable HubSpot for a form, Panther Hook sends eligible, approved production leads to the HubSpot Contacts API. If a contact with the same primary email already exists, Panther Hook updates it instead of creating a new one.
The integration only creates or updates Contacts. It never creates Companies or Deals. Empty and missing field values are skipped so they do not erase existing HubSpot properties.
Connect your HubSpot account
Open your formsStep 1: Select your workspace and form
Sign in to Panther Hook, select the intended workspace and open Forms → your form → Integrations. Choose HubSpot CRM from the native integration providers.
Step 2: Connect securely
Click Connect HubSpot and sign in to HubSpot. Review the requested Contacts permissions and choose the HubSpot account you want to connect. You will return to the form Integrations tab.
You must be a workspace Owner or Admin to connect or disconnect. A connection belongs to one workspace; it is not shared across workspaces.
Step 3: Configure synchronization
Give the destination a name, map the HubSpot contact properties to your form fields, and add the integration. Set the destination to Enabled to start automatic sync for this form.
The current contact mapping expects fields.email as the email source. Other common sources include fields.first_name, fields.last_name, fields.phone, and fields.company. You can map additional supported form fields to writable HubSpot contact properties.
Step 4: Check status and delivery history
Use Test connection to verify permission to read Contacts without creating any test contact. To test actual synchronization, send a synthetic eligible production-mode submission and check that the contact appears in your HubSpot test portal. Remove the synthetic contact after checking.
The latest delivery results appear in the form Integration delivery log. Open full delivery history to inspect failures and retries.
Field mapping example
The mapping shown is illustrative. Select an existing writable property in your HubSpot account for every custom property. Some HubSpot accounts enforce additional required fields or validation rules, including hs_legal_basis (legal basis for processing contact data). If required, explicitly map it from a field containing the appropriate lawful basis. Panther Hook never invents or assumes consent or another legal basis.
A usable email is required to identify a Contact. A submission without one is not sent as a new contact. Dashboard test submissions do not trigger production CRM synchronization.
For HubSpot enumeration properties such as hs_legal_basis, the mapping editor shows allowed API values from your connected HubSpot portal. Supply a matching value from your form data. Do not assume one portal uses the same internal values as another.
{
"email": "fields.email",
"firstname": "fields.first_name",
"lastname": "fields.last_name",
"phone": "fields.phone",
"company": "fields.company",
"my_custom_property": "fields.my_custom_field"
}Permissions, billing, and troubleshooting
- HubSpot needs authorization for Contacts read/write and contact property metadata. Panther Hook stores OAuth credentials encrypted and refreshes them automatically.
- CRM synchronization uses your existing native integration slots and delivery attempt allowance. No separate HubSpot subscription is charged by Panther Hook.
- If a destination remains disabled, check whether HubSpot is connected, your workspace plan allows another integration, and the feature is available in your environment.
- If a lead is missing in HubSpot, check whether it was quarantined or suppressed, then inspect the integration delivery status. Provider rate limiting and temporary errors may trigger retries.
- To use a different HubSpot portal, first disconnect the existing portal. This disables the workspace HubSpot destinations so old pending deliveries cannot be redirected to another account.
- The HubSpot connection test is read-only. A successful test does not prove that custom contact fields are writable.