LanguageENES
HubSpotAvailable on Starter

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. 1

    Create a private app

    HubSpot, Settings, Integrations, Private apps. Copy the service key from its Auth tab. It needs the contacts and companies scopes, read and write, on both the objects and the schemas.

  2. 2

    Connect HubSpot

    In Destinations, paste the key. We verify it before storing it, and Check connection re-asks whenever you want.

  3. 3

    Create a route

    Pick the object, then which leads it takes: one widget, or all of them. The widget also decides which questions the mapper offers, since a widget runs one form.

  4. 4

    Map the fields

    Your form on the left, HubSpot on the right. Auto-map, then check it, and send a sample lead to see what arrives before a visitor does.

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 two forms go to two different places?

Yes. A widget runs one form, so scoping a route to a widget scopes it to that form: put each form on its own widget and each reaches its own object, owner or CRM. A lead can also 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