Turn chat leads into HubSpot contacts.

01

How the HubSpot integration works

HubSpot is a write-only destination: SuperBot pushes contact properties in, and it never reads deals, tickets, or conversations back out. The only read it performs is a contact search by email, so a returning visitor updates their existing record instead of creating a duplicate.

Every selected event is sent the same way, so the event list you choose decides when HubSpot hears about a visitor. Most teams keep “New lead captured” and “Form submitted”, which are the moments a visitor has given an email on purpose.

• New lead captured
• Form submitted
• New conversation started
• Conversation escalated to a human

Highlighted: the events most teams keep for this connector. You choose per connection.

02

What gets sent

Empty fields are left out, so SuperBot never blanks a value that is already on the contact. Events without an email are skipped and noted as an error on the connection card.

03

Connect HubSpot to SuperBot

1. In HubSpot, open Settings → Integrations → Private Apps and create an app. Grant crm.objects.contacts.read and crm.objects.contacts.write, then copy the access token (it starts with pat-).
2. In SuperBot, open Dashboard → Integrations, find HubSpot under “Available connectors”, and select Connect.
3. Paste the token into “Private App access token”.
4. Under “Send these events”, keep only the events you want this connection to receive. All four are ticked by default: new lead captured, form submitted, new conversation started, and conversation escalated to a human.
5. Select “Connect & verify”. SuperBot makes a read-only call to HubSpot's contacts API and only saves the connection if HubSpot accepts the token.
6. Use “Send test” on the connected card. It sends a sample lead (Test Lead, [email protected], Acme Co.) so you can see the contact appear — delete it in HubSpot afterwards.

Don't have a workspace yet? Sign up free — no card needed — then open Dashboard → Integrations.

04

Permissions and privacy

• Scopes: contact read (to find an existing contact by email) and contact write. Nothing else in your HubSpot portal is touched.
• The token is encrypted before it is stored and is never sent back to the browser.
• Chat transcripts are not copied into HubSpot. Only the contact fields in the table above are sent.
• Disable pauses delivery; Disconnect deletes the stored token. You can also revoke the Private App in HubSpot at any time.

05

What teams use HubSpot with SuperBot for

• After-hours lead capture

  A visitor asks about pricing at 11pm, leaves an email in chat, and is a HubSpot contact before your team logs in.

• Keep returning visitors on one record

  Because SuperBot matches on email first, a customer who chats twice updates the same contact instead of creating a second one.

• Feed your existing workflows

  Use HubSpot's own lists and workflows on the contacts SuperBot creates — the automation stays in HubSpot, where you already manage it.

• Website forms without a second tool

  SuperBot form submissions with an email go to HubSpot too, so a simple site form does not need its own HubSpot embed.