Send leads to HubSpot
Connect a private app token, map the fields, and every new lead becomes a contact.
Updated 2026-09-05What you need
A Private App token: HubSpot → Settings → Integrations → Private Apps → Create. Give it the crm.objects.contacts.write scope, and crm.schemas.contacts.read so we can list the properties to map against.
Connect and route
- In Destinations, connect HubSpot with the token.
- Create a route: pick the object (usually Contact) and which widget's leads it takes. Leave the widget empty and it takes every lead.
- Map the fields. Auto-map fills in what it is confident about; check it and fix the rest.
How a lead arrives
Contacts are matched by email, so the same person filling in a form twice updates one record rather than creating two.
A field with nothing behind it is left out of the request rather than sent empty, because an empty value would overwrite what HubSpot already knows about that person.
When it fails
The dispatch log under the routes shows every attempt, what we sent and what HubSpot answered. Common answers:
- 401 or 403. The token was revoked, or it lacks a scope. The connection is marked with an error.
- A property does not exist. Create it in HubSpot, or use New field in the route dialog.
- A required property is missing. The lead had nothing for it. Either map another source or make the property optional in HubSpot.
Network problems and HubSpot outages are retried five times over about two hours. A rejected request is not retried, because sending the same wrong thing again will not fix it.