Send chatbot leads to HubSpot
Every captured lead becomes a contact
When the assistant captures a lead, it goes to HubSpot as a contact without anyone copying it across. Routes decide which widget's leads go where, and the dispatch log shows every attempt.
What it does
Matched by email
The same person filling in a form twice updates one record rather than creating two.
Empty fields are left out
A field with nothing behind it is omitted rather than sent empty, because an empty value would overwrite what HubSpot already knows.
Auto-mapping you can correct
We read your contact properties and fill in what we are confident about. You check it, fix the rest, and create new properties from the same dialog.
How to connect it
Read the full guide- 1
Create a private app token
HubSpot, Settings, Integrations, Private Apps. It needs crm.objects.contacts.write, plus crm.schemas.contacts.read so we can list the properties.
- 2
Connect HubSpot
In Destinations, paste the token.
- 3
Create a route
Pick the object and which widget's leads it takes. Leave the widget empty and it takes every lead.
- 4
Map the fields
Auto-map, then check it. Retries and resends live in the dispatch log underneath.
Questions people ask
What happens if HubSpot rejects a lead?
The dispatch log shows what we sent and what HubSpot answered, and a failed delivery can be resent from there once you have fixed the cause.
Can different widgets go to different places?
Yes. A route binds one widget to one destination, and a lead can go to several destinations at once.
Is the token stored safely?
It is encrypted at rest with AES-256-GCM and decrypted only at the moment a request is signed. It is never returned to the browser.
What teams use it for
Put your knowledge to work today
Free for 14 days. No card, and nothing to install on your site.