Deliver leads to HubSpot
Map the Chat4U form to HubSpot contacts and verify the record that arrives.
2 min read
- Project
- Integrations
- HubSpot
Authorize HubSpot in Integrations, then open the relevant assistant’s Lead capture tab to map and test the fields that will be delivered.
HubSpot is available now. Connect the right OAuth account, map a small visitor form, and confirm the contact ID in Recent deliveries.
- Finish with
- A synthetic HubSpot contact with its delivery record
Connect and map HubSpotFollow the CRM connection guide, then expand HubSpot in Integrations.
Map visitor fields to contact properties such as
email,phone, andcompany; save the mapping and choose HubSpot in the agent’s Lead capture tab. Anamemapped tofirstnameis split into first and last name when possible.Submit a synthetic leadUse a test conversation and values such as `taylor@example.test`.
Select Test connection first if needed, then trigger the configured form. The credential check alone does not create a contact.
Read the outcomeOpen HubSpot’s Recent deliveries and look for the CRM record ID.
A delivered item has the HubSpot contact record ID. Missing required CRM fields usually means the valid-email field or mapping is absent.
Change and recovery rules
- The mapping is project-level, so a change affects every agent that selects HubSpot. Make one change, submit a synthetic lead, then review the delivery log and resulting contact.
- Chat4U queues delivery, records the returned contact ID, and scrubs lead PII from its lead record. Some rate-limit or server errors can be retried by the task system; the UI has no manual retry.
- An invalid grant or missing refresh token marks the integration Needs reconnect. Reconnect and test again.
- Disconnecting stops delivery by clearing stored credentials but preserves the mapping. Turn capture off on agents first if they should stop asking for contact details.
Last updated on