Integrations/HubSpotLast updated
Integration

HubSpot AI that answers pipeline questions and updates records

With Coworker's HubSpot AI integration, ask about deals, contacts and companies in plain English and get answers from live HubSpot data, next to your calls, email and Slack. Agents can then log the note, update the deal or create the record. Changes can wait for your approval, so you see every field before it updates.

How HubSpot context reaches your AI tools

Coworker brings HubSpot together with the rest of your tools in OM2, its organizational memory, then answers in Coworker's own apps, or in Claude, ChatGPT and Cursor through Coworker MCP.

Use cases

What teams do with the HubSpot AI integration

Coworker reads and updates HubSpot next to your calls, email and Slack. Here is what HubSpot AI agents do for each team.

RevOps

Pipeline numbers on request

Ask for open pipeline by stage and owner this quarter and get a report you can share, with stage, pipeline and owner names instead of IDs.

RevOps

Record cleanup

Find deals in Contract Sent with a close date that has passed and get the fixes drafted for approval. A value that is not one of your dropdown options is held back, not written.

Sales leaders

Deal reviews

See which Negotiation deals have gone quiet for 14 days, with each HubSpot record next to its last call and email thread.

Account executives

Notes and next steps

After a call, an agent logs the summary as a note on the deal at the time the call happened, and updates the next step and close date. Each write comes back with a View in HubSpot link.

Customer success

Context before renewals

Get every renewal closing in the next 60 days with its owner, next to what each customer raised lately on calls and in Slack.

Account executives

New records from a call or email

After a first call, an agent creates the contact, company and deal and links them to each other. With approval on, you see every field before it is written.

Sales leaders

A weekly pipeline digest

A scheduled agent posts a Monday pipeline summary, or a list of deals past their close date, to Slack or email without anyone asking.

Everyone

HubSpot in Claude, ChatGPT and Cursor

Connect Claude to HubSpot through Coworker MCP: one connection that also brings in the rest of your tools from 50+ connectors. ChatGPT and Cursor work the same way.

Comparing Coworker with HubSpot's own MCP server? Read our HubSpot MCP guide. More for revenue teams: Coworker for sales teams.

Setup

Live in minutes

1

Connect HubSpot (Read)

Each person signs in to HubSpot from Coworker with their own account. Coworker can then read contacts, companies, deals and activity.

2

Add HubSpot (Write) if agents should edit

A separate sign-in lets agents create and update records and log notes. Skip it and Coworker only reads your CRM.

3

Decide what needs approval

Tick Require approval for HubSpot on an agent. Each change then shows up as an editable card and only runs when someone approves it.

Powered by the Coworker Platform / OM2

Every model needs the right context.

HubSpot's MCP server can only see what lives in HubSpot. OM2 connects that CRM data to the Slack threads, Jira tickets, meeting transcripts, and Google Drive docs around it in one permission-aware knowledge graph, so Claude, ChatGPT, or Cursor starts every task with your customers, projects, and decisions already loaded.

customer14s ago

Mosaic Financial

Series B fintech · $3.1M ARR · 47 seats

24linked
12sources
0.8ssynth
SOC 2 Type II auditPriya NambiarEnterprise onboardingCustomer Success#mosaic-impl
LiveOnboarding kickoff call with Priyavia Gong
Security and governance

Enterprise-grade security, from day one

SOC 2 Type II

Audited annually, report on request

Hosted locally

Your memory stays in your region. Open-source models run in the US.

Isolated per company

In our cloud or your VPC

Never trains on your data

No model provider, closed or open source

Your permissions, enforced

The access already set in Salesforce, Slack, Jira and Drive

Also included

GDPRCASA Tier 2Node-level permissions at query timeEvery fact traceable to its sourceSSO and SAMLAES-256 at rest, TLS 1.2+ in transitRegional data residency

FAQ

Frequently asked questions

Coworker is a context layer for enterprise AI. It connects 50+ work tools, builds a permission-aware company graph called OM2, and runs agents that act across those tools, inside Coworker or in Claude, ChatGPT and Cursor through Coworker MCP.

HubSpot's MCP server is a strong fit if you only need HubSpot in Claude: it reads and writes CRM data and respects your HubSpot permissions. Coworker MCP is for answers that also need Slack, Jira, meeting transcripts or Google Drive, in one connection with HubSpot and the rest of Coworker's 50+ connectors.

Breeze is built into HubSpot and works on what is in HubSpot, including calls and emails logged there. If all of your work happens in HubSpot, it is a strong fit. Coworker is for answers that also live in Slack, Jira, meeting transcripts or Google Drive, and it can write the result back to HubSpot.

Contacts, companies, deals and their activity, plus owners, pipelines, deal stages and the properties on each record, including custom properties. Stage, pipeline and owner IDs are translated into names, so answers read the way your HubSpot views do.

With the HubSpot (Write) connection, agents can create and update contacts, companies, deals and custom objects, log notes, calls, meetings and tasks on a record, and link records to each other. They can also delete a record when asked. Without that connection, Coworker only reads.

You decide. Tick Require approval for HubSpot on an agent and every write from it waits for a person. The approval card shows the record and each field, which you can edit, add to or dismiss before anything runs.

Coworker checks every update against your HubSpot properties before it runs, so changes match how your portal is set up. A dropdown value that isn't one of your options is held back with the allowed options shown, and the approval card shows anything that will be left out.

Each person connects HubSpot with their own login, so Coworker reads and updates HubSpot with that person's access, never a shared admin key. When an admin connects HubSpot for the whole workspace, they choose exactly who can search it.

Yes. An agent can run on a schedule, when a meeting ends, or when someone asks in Slack, and send its results to Slack or email. For example, a Monday pipeline summary, or a weekly list of deals past their close date.

Connecting is a HubSpot sign-in for each person. The only real decisions are which agents can update records and what needs approval. Book a demo, or get a free benchmark of Coworker on your own company data.

Yes. Coworker MCP is one MCP server that gives Claude, ChatGPT, Cursor and any other MCP client the same company context: HubSpot and the rest of Coworker's 50+ connectors, plus OM2, its organizational memory. Every query respects the permissions people already have in those tools, so each client only sees what that person can see.

Sources for HubSpot Breeze, as of October 14, 2026: Breeze Assistant, Agent Hub, HubSpot Credits, HubSpot MCP server, Remote MCP permissions.

Connect HubSpot in minutes

Connect your HubSpot data and watch agents go to work in minutes.