HubSpot
Read and update HubSpot contacts, companies, deals and tickets, with a sign-in or a private app token.
Connect it with: Sign in (OAuth), API key. HubSpot's own documentation: https://developers.hubspot.com/docs/api-reference/auth-oauth-v3/guide.
What agents can do
Connect HubSpot so the agents working your tasks can reach it. With it connected, they can:
- Look up, create and update contacts, companies, deals and tickets through the CRM API.
- Search records with the CRM search endpoint, for example every deal in a pipeline stage.
- Log notes, calls and tasks against a record so the history stays in HubSpot.
- Read pipelines, owners and properties to fill fields the way your portal expects.
Before you start
- A HubSpot account where you are a Super Admin, or may install apps (Connect) or create private apps (a token).
- Knowing which objects agents should touch, so you can tick only those scopes.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with HubSpot
This is the quickest way in: you sign in to HubSpot and approve what Jaah asks for. You never copy a key.
- In Jaah, open Secrets and select New.
- Search for HubSpot and select its card.
- Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
- Select Connect HubSpot. HubSpot's sign-in window opens.
- Sign in to HubSpot if asked, check the access listed, and approve it.
- You land back in Jaah on the new secret, which reads Connected once its test passes.
If the button reads Jaah app not configured, this Jaah has no app registered at HubSpot yet. Use an API key, or your own OAuth app, until it does.
Scopes Jaah requests
Jaah asks HubSpot for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.
| Scope | Why Jaah asks for it | Required |
|---|---|---|
oauth | Sign in to HubSpot and keep the connection: HubSpot requires it on every app | Yes |
crm.objects.contacts.read | Read contacts | Yes |
crm.objects.contacts.write | Create and update contacts | Yes |
crm.objects.companies.read | Read companies | Yes |
crm.objects.companies.write | Create and update companies | Yes |
crm.objects.deals.read | Read deals | Yes |
crm.objects.deals.write | Create and update deals | Yes |
tickets | Read and update tickets | Yes |
Connect with an API key
Prefer this when you cannot sign in with HubSpot — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.
Find each value first:
- Access token: In HubSpot, select the settings gear, then Integrations > Private Apps (in newer accounts this lives under Development > Legacy apps), select Create a private app, name it Jaah, tick the scopes agents need on the Scopes tab (for example crm.objects.contacts.read and crm.objects.deals.write), select Create app, then on the Auth tab select Show token and copy it.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the HubSpot card.
- Name the secret and choose who can use it.
- Select Use an API key instead.
- Fill in Access token.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Register your own OAuth app at HubSpot when your company requires apps it controls, or before this Jaah has an app registered there.
- Create an OAuth app in HubSpot's developer console, https://developers.hubspot.com/ (HubSpot's documentation).
- Set its redirect URI to
https://app.jaah.ai/api/credentials/connect/callback(on your own Jaah, its console address followed by/api/credentials/connect/callback). - Give it the scopes in Scopes Jaah requests.
- Copy its client ID and client secret.
- In Jaah, start a new HubSpot secret, select Use your own OAuth app, paste both values and select Connect HubSpot.
The client secret is stored with the connection, encrypted, like any other secret value.
Test the connection
Select Test on the secret. Jaah calls HubSpot's API once (GET https://api.hubapi.com/account-info/v3/details) with the stored values, and shows who it answered as, or which value HubSpot refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.
A key connection hands the agent its fields: access_token.
Tell the agent in your task description which secret to use, for example “use the HubSpot secret org/hubspot”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at HubSpot once the test passes. Steps: Replace or delete a secret.
- Reconnect: when HubSpot ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at HubSpot's side too, revoke Jaah in HubSpot's settings, or revoke or delete the key at HubSpot.
Limitations
- Connect signs in as you and reaches the portal you pick at consent; agents act with your HubSpot permissions. A private app token acts as the app instead.
- The token reaches only the scopes you ticked on the private app; adding a scope later needs no new token, but agents see the change only after you save the app.
- HubSpot limits private apps to a per-account request rate (for example 100 requests per 10 seconds on Professional), shared by everything using that app.
- A private app belongs to one HubSpot account; connect a separate secret for each portal, including a sandbox.
- Agents can do only what the connected HubSpot account and its granted scopes allow.
Troubleshooting
The HubSpot window warns that the app is not verified
Jaah's app is unlisted on the HubSpot Marketplace. Type I accept the risk if HubSpot asks, then select Connect app.
Test says HubSpot rejected the access token
The token was rotated or the private app was deleted. In HubSpot open the app's Auth tab, copy the current token, and select Replace on the secret.
Test passes but an agent gets 403 MISSING_SCOPES
The private app lacks the scope that call needs. Open the app's Scopes tab in HubSpot, tick the missing scope (the error names it), and select Commit changes; the token stays the same.
Agents hit 429 TOO_MANY_REQUESTS
The account's private-app rate limit is spent. Ask the agent to batch reads with the batch endpoints, or give heavy jobs their own private app.
Still stuck? Select Test and read the result: it names the value HubSpot refused and the status it answered.
FAQ
Should I connect or paste a private app token?
Connect is quicker and renews itself. Use a private app token when agents should act as an app rather than as you.
Which portal does Test name?
Test shows the portal ID the token belongs to, so you can tell a sandbox from production at a glance.
Does rotating the token in HubSpot break running tasks?
Yes, once the old token expires. Rotate in HubSpot, then select Replace on the secret straight away; new calls use the new token.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one HubSpot account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.