AI Agents for HubSpot: 5 Workflows That Actually Earn Their Keep
Five AI agents for HubSpot built around deal-stage tracking, post-call CRM updates, and at-risk-deal Slack digests, plus how to build the first one on Major.

What are the best AI agents for HubSpot?
The best AI agents for HubSpot sit between systems and make one judgment call a rep or manager would otherwise make by hand. Five workflows earn their keep first: a deal-stage tracker, a post-call CRM update, inbound lead enrichment, an at-risk deal digest, and a quote-to-contract handoff. Each wakes on a HubSpot event, pulls context from Gong, DocuSign, Apollo or Stripe, and ends in a Slack message or a gated CRM write.
Major is where you build these. The agent figures out the workflow once, then builds a governed app for the repeatable part: the webhook endpoint, the association lookups, the filters and the Slack post. That app runs as deterministic code with its own database and audit log. The model is called only for the judgment, such as summarizing a Gong transcript. This guide is for RevOps and sales operations leads who want that working against their own portal.
HubSpot's own Breeze agents handle tasks inside HubSpot. The workflows below span other systems with logic you define, which is where a custom agent on Major fits.
The five workflows
- Deal-stage tracker: triggers on a deal stage change, uses HubSpot, Gong, DocuSign and Slack, suits sales managers.
- Post-call CRM update: triggers when a Gong call ends, uses HubSpot, Gong and Slack, suits account executives.
- Inbound lead enrichment: triggers on a form submission, uses HubSpot, Apollo and Slack, suits sales and marketing ops.
- At-risk deal digest: runs on a daily schedule, uses HubSpot, Gong and Slack, suits sales managers.
- Quote-to-contract handoff: triggers when a DocuSign envelope is signed, uses HubSpot, DocuSign, Stripe and Slack, suits account executives.
1. Deal-stage tracker
When a deal moves backward a stage, this agent assembles the story. It pulls the latest Gong call for the associated contact and the DocuSign envelope status, then posts a short Slack brief: what changed, how the last call sounded, whether paper is stuck.
The hard part is association resolution. The deal webhook gives you a deal ID, not the contact, so you fetch associations before you can ask Gong anything.
2. Post-call CRM update
After a Gong call ends, the agent drafts the deal note a rep would type from memory. It reads the transcript, summarizes outcome and next step, and posts the draft to the rep in Slack with an Approve button. Approve writes the note to HubSpot. Ignore it and nothing happens.
The real work is the summarization prompt. A transcript is long, and most of it is not a deal note.
3. Inbound lead enrichment
A form submission arrives with an email and little else. The agent enriches it against a provider like Apollo, scores intent from firmographics and form context, writes enrichment fields back to the contact, and routes hot leads to the right rep in Slack. Enrichment fields are additive and easy to correct, which makes unattended write-back reasonable here.
4. At-risk deal digest
Every morning one Slack message lists deals stalled past your threshold and deals where the last Gong call carried negative sentiment. This one runs on a schedule, because a daily report is different from polling HubSpot to detect edits. The trap is the threshold. Set "stalled" too tight and the digest becomes noise.
5. Quote-to-contract handoff
When a deal hits closed-won and its DocuSign envelope is signed, the agent confirms the signature, updates the deal, optionally starts billing in Stripe, and tells revenue ops in Slack. Closed-won in HubSpot and signed in DocuSign rarely happen at the same instant, so the agent keys off the DocuSign signature event and reconciles back to the deal.
What to know about the HubSpot API first
Use a private app token for an internal agent. OAuth is for apps you distribute into other portals. Three endpoint groups cover most agents: the CRM Objects API for deals, contacts and companies, the Webhooks API for subscriptions, and the Engagements API for notes, calls and tasks.
Use webhooks, not polling. A webhook arrives as a JSON array of changes, and a deal stage change carries subscriptionType: "deal.propertyChange", an objectId, a propertyName and a propertyValue. Nothing else. To learn the amount, owner or associated contact, call the CRM API with that objectId. Plan for the extra fetch.
The gotcha that bites most teams: subscriptions are scoped to a single object type. A deal.propertyChange subscription stays silent when an associated contact's email or title changes. Register a separate contact.propertyChange subscription and resolve the association yourself. HubSpot added association-change events, but they fire when the link between records changes, not when a property on the related record does. Custom objects also need Enterprise. Check HubSpot's Webhooks API docs before you design around any of this.
Build the deal-stage tracker on Major
Here is the first workflow end to end on Major.
- Connectors: HubSpot, Gong, DocuSign and Slack, each added once with its own scoped credential.
- The app that holds state: a deal-brief app with a managed database table of deals seen, the brief posted, the button clicked and who clicked it. It is the control surface a manager can open, and the history survives between runs.
- The trigger: a HubSpot webhook on
hs_pipeline_stage, filtered in code to deals over $25,000 whose stage moved backward. - Deterministic steps: fetch the deal and its associated contact, get the latest Gong call from the last 14 days, flag a DocuSign envelope left unsigned for more than 7 days. If no call exists, skip it and continue. This runs as code, the same way every time.
- The agent's judgment: one model call summarizes the deal in 80 words from the deal record, call summary and envelope status, and returns a sentiment, a blocker and a suggested next step.
- The Slack gate: the brief posts to
#revopswith Approve next step, Hand to manager and Snooze buttons. Approve writes a deal note to HubSpot. Both writes are human-gated. - Governance: HubSpot gets deals read and a write scope limited to notes, nothing that can move a stage. Gong is read-only, DocuSign is envelope-read, Slack posts but does not read. RBAC controls who can edit the app, and every call is audit logged.
Reason once, run forever. The agent works out the association lookups and filters the first time, then the app handles them on every deal after. Token cost is front-loaded, then flat. The other four workflows have the same shape, so each one you build is a template for the next. Start building on Major.
Where to start
Start with the deal-stage tracker or the at-risk digest. Both only read from HubSpot and write to Slack, so you can prove the value before any record changes. Move to enrichment next, where write-back is low risk.
None of these let the agent write free-form generated text into HubSpot fields unattended. That carries its own guardrails and is a separate problem.
Start building on Major
Build the HubSpot deal-stage tracker on Major: a webhook trigger, a governed app that remembers every brief, and one model call only where judgment is needed. Or see it against your own portal with our team.
Related articles
Frequently asked questions
- Does HubSpot have its own AI agent?
- Yes. HubSpot Breeze includes Breeze Agents for prospecting, customer and data tasks, the Breeze Assistant copilot, and Breeze Intelligence for enrichment. Breeze suits work inside HubSpot. For workflows that span Gong, DocuSign, Stripe or Slack with logic you define, build a custom agent against the HubSpot API. On Major that agent becomes a governed app with a scoped HubSpot token and an audit log of every CRM call.
- What's the difference between a HubSpot Workflow and an AI agent?
- A HubSpot Workflow runs fixed rules: if a property equals X, do Y. An AI agent reads context a rule cannot encode, like the sentiment of a Gong transcript, then acts on instructions you wrote. Use Workflows for fixed flows and an agent when the next step needs judgment. Major splits the work the same way: the model makes the call, and the fetches and Slack post run as app code.
- Can AI agents update HubSpot records automatically?
- Yes, through the HubSpot API, but route writes through a human approval gate or limit the agent to low-risk fields like enrichment data. Enrichment is additive and easy to correct. Free-form text written into deal notes without review is where teams get hurt. On Major, a scoped credential can carry deals read and notes write and nothing that moves a deal stage.
- How do you trigger an agent from a HubSpot deal change?
- Subscribe to a webhook instead of polling. A deal.propertyChange subscription on hs_pipeline_stage fires when the stage moves, and the payload gives only an objectId, the property name and the new value. Call the CRM API for the amount, owner and associated contact, and filter early. Major hosts that webhook endpoint inside the app, so the fetch, filter and retry logic are code.
- What are the limits of HubSpot webhooks for agents?
- Subscriptions are scoped to one object type, so a deal.propertyChange subscription stays silent when an associated contact changes. Register a separate contact.propertyChange subscription and resolve the association yourself. Association-change events fire when a link changes, not when a related record property does, and custom objects need Enterprise.