Руководства
Keep HubSpot current from every conversation
Create a private app token, connect it in the Console, and let hand-offs open tickets while resolved conversations keep each customer's record up to date.
Loading…
Руководства
Create a private app token, connect it in the Console, and let hand-offs open tickets while resolved conversations keep each customer's record up to date.
Busymate AI 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.
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.
Open Console → Connections 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.
| Field | What it changes |
|---|---|
| Portal ID | Your account id, the number that follows app.hubspot.com/contacts/ in the URL. Supplying it makes links from a conversation open the matching object in your own account. |
| Ticket pipeline ID | Which pipeline a raised ticket enters. Leave it empty and the account default is used. |
Neither is required. A connection holding only a token is complete.
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.
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.
Not yet. The card accepts a private app access token and nothing else today; an OAuth app is on the roadmap and will be announced in the changelog.
No. A contact is only ever written for a visitor your own site has identified. Every other conversation produces a ticket with no contact behind it.
The job waits instead of failing. Attempts are retried with a widening gap, and an unconnected account holds the work rather than discarding it, so the queue catches up once you save.
No. Only the final characters are ever shown. If you lose the value, create a new private app token in HubSpot and paste it over the old one.