A HubSpot connection lets the Create, update or find a record step work with contacts, companies, deals and tickets in your HubSpot account. It connects with a private app token that you make in HubSpot.

Who can do this

  • In Bizomate: workspace Admins and Editors.
  • In HubSpot: a Super Admin of the HubSpot account, who can create private apps.
  • Plan: HubSpot is a premium connection. You can add it and test its steps on any plan; publishing a workflow that uses it needs Starter, Pro or Enterprise.

Steps

In HubSpot, make the token:

  1. Sign in to HubSpot and select the Settings icon in the top bar.
  2. In the menu on the left, go to Integrations, then Private apps. If your account shows them elsewhere, search the settings for "private apps".
  3. Select Create a private app.
  4. On Basic info, type a name — for example Bizomate — and a description if you like.
  5. Open Scopes and tick, under CRM, the read and write scopes for each object your workflows will use:
    • Contacts: crm.objects.contacts.read and crm.objects.contacts.write
    • Companies: crm.objects.companies.read and crm.objects.companies.write
    • Deals: crm.objects.deals.read and crm.objects.deals.write
    • Tickets: tickets
  6. Select Create app, then Continue creating.
  7. On the app's page, select Show token (or Copy) to copy the access token. It starts pat-.

In Bizomate, add the connection:

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under CRM/Sales, select HubSpot. The window shows "Private app token".
  3. In Connection name, type a name — for example Consulace HubSpot.
  4. Paste the token in Private app token. "Made in HubSpot under Settings › Integrations › Private apps. Give it the CRM scopes for the objects you will use. Stored encrypted; never shown again."
  5. Leave Test the connection before saving ticked.
  6. Select Save connection. It reads Testing while HubSpot is asked.

The toast "Connection added" says "“Consulace HubSpot” is ready. Every workflow in this workspace can use it."

What happens next

  • The connection appears under CRM/Sales. Its panel shows Test, Revoke and the masked token's ending, never the token.
  • The Create, update or find a record step lists it under Connection, and loads the object's fields — custom properties included — from your account.
  • Test answers "HubSpot accepted the private app token."

Good to know

  • On the Free plan the window notes: "HubSpot is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
  • The token is tried against your HubSpot account before it is saved. A token HubSpot refuses is never kept.
  • To replace the token — after rotating it in HubSpot, say — Revoke the connection, then Reconnect it and paste the new token. The field shows the ending of the one being replaced. Workflows using it fail between the two, so do both together.
  • If you later add a scope in HubSpot, the token stays the same; nothing changes in Bizomate.

If something goes wrong

What you see Why What to do
HubSpot refused it — "HubSpot refused the connection: … Reconnect it, or replace the token. Nothing was saved." The token was mistyped, rotated or deleted in HubSpot. Copy the token again from the private app and paste it.
"HubSpot refused: … The token or sign-in lacks a scope this needs." The private app is missing a scope for that object. Add the scope in HubSpot (step 5 above).
"Could not reach HubSpot: …" HubSpot did not answer. Try again in a few minutes.
"HubSpot did not answer within 30 seconds." HubSpot was slow. Try again.
"Enter the credential." Private app token is empty. Paste the token.