Keep HubSpot current from every conversation

Coming soon. The HubSpot connector is not live in the Console yet — this guide is the plan for how it will work once it ships, so you know what to expect and can prepare the private app ahead of time. Nothing below can be done today.

AI Assistant writes into the HubSpot account your team already works in: a request for a person raises a ticket, a resolved conversation adds a timeline note to the customer's record, and the assistant can read that record back while it answers. A workspace admin wires it up once from the Console, with your own credential and nobody else's.

1. Create a private app

In HubSpot, open Settings → Integrations → Private Apps and choose Create a private app. Name it so your colleagues recognize it later, then grant three scopes: crm.objects.contacts.read, crm.objects.contacts.write and tickets. HubSpot reveals the access token once — copy it before closing the dialog.

There is no marketplace listing to install and no consent screen to approve: a private app token is the whole credential today. An OAuth app is planned, and the changelog records it when it lands.

2. Paste the token into Connections

Open Console → HubSpot and find the HubSpot card. Paste the access token and save. From then on the value is write-only — the card shows only its final characters, never the token, and pasting a fresh one rotates the previous one out.

3. Add the two optional details

Neither is required. A connection holding only a token is complete.

4. Send a test ticket

The card carries a Send test ticket button. It exercises the real path — credential, account, pipeline — and a ticket surfaces in HubSpot within seconds. Press it after the first save, and again after any rotation.

5. What reaches your CRM, and when

• A visitor asks for a person. A ticket is raised holding the conversation so far and the page that visitor was reading.
• Your site has already identified them. The ticket names them, and once the conversation is resolved their contact is created if new or updated if it exists, gaining a timeline note with the exchange.
• The visitor is anonymous. No contact is invented — no placeholder address, no stand-in name. The ticket simply arrives unattributed, so your database stays a record of customers instead of a log of traffic.

6. What the assistant reads back

Answering someone your site has identified, the assistant may look up that person's existing contact and their open tickets, so it can say where a request stands rather than making the customer repeat it. The look-up is read-only, and it is unavailable for an anonymous visitor.

Verify

1. Save the token, press Send test ticket, and find the ticket in HubSpot.
2. On your own site, signed in as a test customer, ask to talk to a person. A ticket is raised naming that customer.
3. Resolve that conversation from the Inbox, then open the contact in HubSpot — its timeline carries a note with the exchange.
4. Repeat step 2 signed out. The ticket arrives with nobody attached, and your account gains no new record.
5. Rotate the token in HubSpot, paste the replacement, and confirm a test ticket still lands.

Next

• Recognize signed-in customers — identity is what turns a ticket into a contact.
• Set up human handoff — the moment that raises the ticket.
• Connect your MCP server as assistant tools — reach the rest of your systems.