An AI Agent for HubSpot: A Monday Pipeline Review That Writes Itself

Every sales team has the Monday meeting where someone scrolls through HubSpot asking "what's happening with this one?" This recipe replaces the scrolling. An agent reads the pipeline before the meeting, lists the deals that have gone quiet, suggests a next step for each from the deal's own history, and has it waiting for you in a thread where you can ask about any deal.

It reads the CRM. It does not write to it, unless you later decide it should.

What you'll end up with

Every Monday at 8:00, a chat thread from @pipeline that opens with something like:

4 deals stalled this week. Northwind (Maya, $42k, 19 days idle): last touch was the pricing doc; suggest a 15-minute call to walk the procurement questions. Contoso (…)

Then an offer to draft the follow-up for any deal, or to dig into one deal's history. Setup is about fifteen minutes.

Step 1: Connect HubSpot

In Integrations, choose HubSpot and approve the OAuth prompt. Damon discovers the actions HubSpot exposes — searching and reading deals, contacts, companies, engagements, and creating or updating them — and classifies each as a read (crm.read) or a write (crm.write). Reads are auto-approved by default. Writes require approval by default, and this recipe doesn't need any.

Step 2: Create the agent

In Agents, create:

• Name: Pipeline Reviewer, @pipeline
• Personality: "Direct. Numbers first. One line per deal. Suggest a next step only when the deal's history supports it; otherwise say what's missing."
• Goals: "Make sure every open deal has recent activity, an owner, and a next action. Surface the ones that don't."
• Integrations: HubSpot.

Or describe that to Damon in chat and approve the agent it proposes.

Step 3: Ask once, by hand

Before scheduling anything, run the question in chat so you can tune it:

Look at open deals in HubSpot. Which have had no activity in the last 14 days? For each, give me: deal name, amount, owner, days since last activity, and one suggested next step based on the last few engagements.

Check the answer against HubSpot. If it's counting deals you'd exclude (a "closed lost" stage that isn't marked closed, a parked enterprise deal), add that to the instructions now. This is also when you find out whether 14 days is the right threshold for your cycle.

Step 4: Schedule it

Ask the agent: "Run this every Monday at 8am and message me the result." Damon builds a workflow:

1. Trigger — every week, Monday, 08:00, your timezone.
2. Agent step — the tuned question above, run in the background with the HubSpot tools. Its output is the structured list.
3. Message step — opens a thread in Damon: count of stalled deals, the list, then the offer to draft a follow-up or dig into a deal.

Everything here is a read, so the workflow runs without asking. If the team wants the list in a Slack channel, connect Slack and add that to the message step's offer; posting is a message.send action, so it asks before anything reaches the channel.

Making it smarter over time

• Classify before you list. Add a structured-output step that tags each stalled deal as needs-call, needs-proposal, waiting-on-them or probably-dead, then a conditional so probably-dead deals go to a separate "close these?" section instead of cluttering the list. Damon's workflow editor supports this classify-then-branch pattern directly.
• Let it write, narrowly. Once you trust the next-step suggestions, grant crm.write for one specific action, such as creating a follow-up task on the deal, while keeping everything else gated.
• Save your preferences as a skill. "Sort oldest-idle first. Never more than ten deals. Amounts in $k." Save that once and every pipeline question the agent answers, scheduled or not, follows it.

Variants

• Pipedrive: identical setup; connect Pipedrive instead of HubSpot.
• Per-rep versions: one workflow per owner, sending each rep their own stalled deals on Monday morning, with the manager's roll-up at 9.
• Deal-desk questions in chat: the same agent answers "what did we last say to Northwind?" on demand, with citations to the engagement records.

Common questions

Does the agent change anything in HubSpot?

Not in this recipe. It only uses read actions. Any write is gated by default and you'd have to grant it explicitly.

How does it decide the "next step"?

From the deal's engagement history: the last emails, notes and meetings logged on the deal. If there isn't enough to go on, a well-written agent says so rather than inventing one; the personality line "otherwise say what's missing" is there for that reason.

Can it run more often than weekly?

Yes: every 15 minutes up to monthly. Weekly matches most pipeline rhythms; daily is useful in the last week of a quarter.

What does it cost to run?

A run like this reads a few dozen records and writes a short summary, which is a small number of credits. The free plan's credits cover a couple of weeks of daily runs.