CRM & sales
Connecting HubSpot to an Autonomous AI Agent
An Atako agent connected to HubSpot can read and update contacts, companies, deals, and tickets, but only the objects and actions covered by its grant.
Possible workflows
Enriching and qualifying inbound leads
As soon as a contact lands in the CRM, the agent retrieves it with get_contact, cross-references the available information, updates its properties (update_contact), logs a qualification note (create_note), and creates a follow-up task for the relevant sales rep (create_task). The rep keeps control of the call or email; the agent just spares them the data entry and prior research that normally precede a useful first contact, which often gets pushed back for lack of time in the day.
Following up on deals stalled in the pipeline
The agent searches for deals with no movement in a given number of days (search_deals, list_pipelines to know the stages), creates a follow-up task for the deal's owner identified via list_owners, and can update the status if a clear rule justifies it (update_deal). Nothing moves without leaving a traceable record in the CRM, which prevents pipelines bloated with ghost deals no one is actually following up on.
Creating support tickets tied to an account
From a signal received by email or Slack, the agent creates a ticket (create_ticket), links it to the right contact and company (create_association), then tracks its progress and updates it as the conversation moves forward (update_ticket). The ticket stays visible and editable by the support team like any other, with the account's full history already attached from creation.
Connector actions
get_contact (read)
Retrieves a CRM contact by ID.
search_contacts (read)
Searches contacts by text or property filters.
get_deal (read)
Retrieves a CRM deal by ID.
list_deals (read)
Lists CRM deals, paginated.
list_pipelines (read)
Lists pipelines and their stages (deals or tickets).
list_owners (read)
Lists CRM owners, filterable by email.
create_contact (write)
Creates a CRM contact.
update_contact (write)
Updates a contact's properties.
create_deal (write)
Creates a CRM deal.
update_deal (write)
Updates a deal (stage, amount).
create_ticket (write)
Creates a support ticket.
create_task (write)
Creates a CRM task (follow-up, call).
create_note (write)
Logs a note, to be associated with a record.
create_association (write)
Links two CRM records together.
Prerequisites
- A HubSpot account with super admin rights to create a private app.
- Create a private app under Settings then Integrations then Private Apps.
- Select the scopes needed (contacts, companies, deals, tickets, owners, read/write).
- Copy the access token shown after creation (prefixed pat-).
- In Atako, an integration admin role is needed to grant the permission to the agent.
How to connect
- 1
Create the HubSpot private app
Under Settings then Integrations then Private Apps, create an app, name it, then choose its scopes in the dedicated tab.
- 2
Generate and copy the token
Once the app is created, reveal and copy the access token (pat-...), shown only once.
- 3
Connect HubSpot in Atako
Under Settings then Integrations, paste the access token.
- 4
Grant the permission to the agent
From the agent's page or from the connection, select the precise authorized actions and their scope (read-only or read and write).
Why Connect an Autonomous Agent to HubSpot
HubSpot centralizes contacts, deals, and tickets for a sales or support team. The repetitive work that goes with it, enriching a record, following up on a stalled deal, creating a follow-up task, usually gets done piecemeal, whenever someone remembers to. An Atako agent connected to HubSpot through tool calling does this work continuously, in its own environment, without waiting for a rep to open their morning task list.
The difference from a classic automation scenario: the agent runs continuously and makes a decision, not just an isolated action. It can receive a signal by email or Slack, look up the relevant contact or deal in HubSpot, decide whether to create a task or update a property, and then do it, within the exact scope of the actions it's been granted.
The HubSpot connector covers 37 actions according to Atako's documentation (17 read, 20 write), from searching contacts to creating custom properties. The most direct product use case: a RevOps automation agent that monitors the pipeline, enriches leads, and flags data anomalies without constant manual intervention.
Limits and Best Practices
The HubSpot API enforces rate limits that vary by the company's HubSpot subscription (number of requests per ten-second window, and per day), with even stricter thresholds on search endpoints. An agent processing a large volume of contacts needs to spread its calls out rather than doing everything at once.
Some write actions, like delete_contact or delete_deal, are irreversible on the HubSpot side once executed. They're only usable if the agent's grant explicitly authorizes them, which stays rare in practice for this type of action.
As with every Atako integration, the connection alone grants no access: a precise grant is needed (agent, action, scope). See the permission model and plans to scope this before connecting the agent to your CRM.
Related use cases
Related integrations
Frequently asked questions
Can the agent send marketing emails from HubSpot?
It can create a marketing email draft (create_marketing_email) if that scope is granted, but nothing goes out without a send action approved by your team: the connector has no direct marketing-email-send action.
Do you need a paid HubSpot plan to connect the API?
The API and private apps are available starting with HubSpot's free plan for standard objects. Some advanced scopes, like creating custom properties, can depend on the pricing tier subscribed to.
How do you revoke the agent's access to HubSpot?
Delete or deactivate the private app on the HubSpot side, or revoke the connection on the Atako side. Access is cut off immediately and permanently for every agent that was using it.
Can the agent delete contacts from the CRM?
Yes, the delete_contact action exists, but only if the agent's grant explicitly authorizes it with write scope. By default, no action is granted: you decide whether deletion falls within the agent's scope.
What to read next
Sources
- HubSpot Developer Docs, Private apps · accessed on September 4, 2026
- HubSpot Developer Docs, API usage guidelines and limits · accessed on September 4, 2026
CTO at Atako
This content was written by Atako's AI agents, then reviewed, corrected, and approved by Romain Laodicina, CTO of Atako.