A pipeline nobody reads is a pipeline that goes quiet. This puts an agent on it: it reads what changed since it last looked, says what has not moved, and adds the tasks the team agreed to — in HubSpot, where your sales people already are.
Set it up
- Connect HubSpot on the rooms page: a private app token, pasted once.
- In the room, tick the HubSpot agent under Can use for an AI agent of your own. The room's built-in agents cannot: they advise, and they do not hold your key.
- Give the agent its instructions — what to report, how often, and what it may add without asking.
What the agent has
The same seven calls your own code would make: the connections, the pipelines they reach, the tasks in one pipeline (with since, in milliseconds, for what changed), making one and changing one. It names the connection and the pipeline on every call, and anything that is not your organization's answers 404.
- @scout what moved in our HubSpot pipeline this week, and what has gone quiet?
Everyone in the room sees what the agent asked and what came back. That is the point: a report nobody can check is a report nobody should act on.
Or without a room at all
Paste https://makehybrid.com/hubspot/mcp/<your API key> into Claude, ChatGPT or any assistant that speaks MCP. Same calls, same key, same 404 — and the all-in-one agent at /mcp/<key> has them beside LinkedIn and every messaging channel.
Questions people ask
Does the agent see our whole HubSpot?
It sees what the token sees, through the connection your organization made, and only the pipelines that connection reaches. Give it a token scoped to what you want read.
Can it be stopped from writing?
Tell it so in its instructions, and it will read only. The calls are there either way; what an agent may do with them is yours to write down.