HubSpot Deal Watch Agent with Claude Code

The first instruction is a gate: establish that the stage actually changed, and end the run there when it did not. Everything else in this agent is conditional on passing it. Claude Code is reliable on structured sequences of that sort, which matters when the correct behaviour on most events is to do nothing and say nothing.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

Watch it work before it's live

Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
C

Camila Rojas

Banco Sur renewal, three year term

EmailEnterprise pipeline, Decision Maker Bought-In to Contract Sent

Note145,000 USD, close date 30 September, moved this morning after 41 days in Decision Maker Bought-In. The most recent activity is a note from Camila saying procurement has signed off and the master agreement is sitting with their legal team. Three other open deals exist against the same company.

What you'll need

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect HubSpot

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Pipeline rules

    How your pipeline is meant to move: which stages carry a clock and how many days it runs for, the deal size that earns its own line, what you expect to be filled in when a deal closes lost, and which moves are routine enough to pass without a message.

  4. Runs on Claude Code

    Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

A considered pairing

Why Claude Code for this agent

Interesting is not movement

A logged call and a corrected amount both carry real content and neither is a move. Stopping on an event full of substance is a discipline rather than a shortcut.

Order loaded, then direction

Forwards or backwards is knowable only from the pipeline sequence, so the pipeline is fetched before the move is described. Multi step work in a fixed order is this harness at home.

Good to know

Before you fork

A rep drags a deal into the wrong stage and pulls it back a minute later. Two messages?

Two stage changes really did happen, so two events arrive and both pass the gate. What bounds the noise is your rules, since moves inside the same part of the pipeline can be declared routine and pass without a line. A correction into and out of a stage that carries a clock is arguably worth seeing anyway.

Other editions

Run it with a different agent

OpenAICodexopencodeopenclawhermesMore Claude Code agents

Make it yours

Put HubSpot Deal Watch Agent to work on Claude Code.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.