Claude, Meet HubSpot. Properly This Time.
The connector is the front door. Here’s the rest of the house.
You connected Claude to HubSpot. It answered a question about a deal. Everyone was impressed for about a day. Then someone asked it to update 4,000 records overnight without a human clicking “confirm” on each one, and the connector politely declined.
That’s not a bug. The MCP connector is built for conversations, not operations. If you want Claude running agents against your CRM on a schedule, or HubSpot calling Claude mid-workflow, you need a different connection. We’ll show you which one, and when.
What you will leave with:
A clear map of the four ways Claude connects to HubSpot, and what each one can and can’t do
A working pattern for running Claude agents against HubSpot without someone babysitting the chat window
A rule of thumb for which connection to use, so you stop building cron jobs for things a chat could handle (and vice versa)
Who this is for:
RevOps leaders, HubSpot admins, and GTM engineers at Series A to D B2B SaaS companies already using Claude. If you haven’t connected the two yet, start with the connector and come back. We’ll still be here.
Your hosts:
Alex Biale, Co-Founder, Domestique. Leads AI strategy, and has broken more test portals than he’ll admit.
Connor Griffith, HubSpot Service Lead, Domestique. Fixes them.
Register here
11/12 @ 11a MT
