Skip to main content
The HubSpot Tool lets DinoAI work with your CRM records the way it already works with Jira tickets and Notion pages: looking up the customers behind the data, and writing back what it finds. It is most useful when the question spans your warehouse and your CRM, such as reconciling a revenue model against the deals that produced it, or annotating an account with what a data investigation turned up.
Requires the HubSpot integration. Connect it under Settings → Integrations. The Personal card connects your own HubSpot account for the copilot in the Code IDE; the DinoAI agent card connects a workspace-level account for Slack, Programmable, and Bolt pipeline agents. See Connecting integrations.

​
Capabilities

Every tool works across the standard CRM objects (contacts, companies, deals, and tickets) and accepts custom object type ids, so the same set covers your whole CRM.
Every HubSpot call asks first. Reads and writes alike surface an approval card in the chat panel before they run, the same way Jira and Linear calls do. Writes use HubSpot’s default associations, and when HubSpot rejects a call (for example an unknown property) it passes the reason back so DinoAI can correct itself rather than failing silently.

​
Using the HubSpot Tool

  1. Connect HubSpot under Settings → Integrations, on the Personal card for the copilot or the DinoAI agent card for agents.
  2. Open DinoAI and describe what you need in terms of your CRM, naming the object type where it helps.
  3. Approve each HubSpot call as DinoAI makes it.

​
Example use cases

Finding the deals behind a number
Result: DinoAI searches deals with a close-date filter, resolves the owner ids to people, and lists them. Reconciling the CRM against your warehouse
Result: DinoAI queries the model with the warehouse tool, searches the matching HubSpot companies, and reports the gaps. Writing findings back
Result: DinoAI creates the note and attaches it to the record, after asking you to approve the write.

​
Over MCP

The five read-only tools (search, get, list properties, list owners, and get associations) are also available through the Paradime MCP server, so Claude, Cursor, or any other MCP client can query your CRM through Paradime. The write tools are not exposed over MCP, because each one depends on an approval step an MCP client cannot present.