Connect an AI agent to HubSpot: How a SalesOps Lead Fired Her BI, Commissions, and Forecasting Tools

It’s Monday morning. Hila, the Sales Operations Manager at Agora (a real estate investment management software), just turned on her computer. Ping. Ping Ping.

Her Slack channel fills up with exactly what she needs. Every closed-lost deal from the last seven days, the exact explanations why (with actual data, not just the Account Executive’s generic reasoning), and overall trends. The report shows just the deals her team owns. No sensitive data was left exposed in the making. 

She did not have to dig for answers. An AI agent did everything while she was sleeping. All she did was connect an AI agent to Hubspot. 

Her chosen agent? Claude. 

Her connector? HubSpot. 

The result? She nixed her BI, commissions, and forecasting tools. Getting rid of the forecasting tool alone has since saved the company $15,000/year. She has everything she needs to make informed business decisions, without having to go find it. 

Want to know how she did it? She tells all. 

Most importantly, she shares how she did it without compromising the company’s entire CRM. The Claude HubSpot connector is scoped to the records she owns. 

What RevOps teams actually do with HubSpot and AI agents

"I use Claude every day for everything,” Hila tells us from the jump of our conversation. With a Claude HubSpot connector, she is able to manage real workflows. Leading Sales Operations at a top-tier real estate investment company means she needs to make sure all data is secure. She can confidently say it is. 

If you’ve ever asked, “What can AI agents do in Hubspot?” let’s take a look at a few of her most pivotal use cases: 

1. Closed-Lost Analysis in Hubspot with AI 

Cadence: Scheduled weekly

Running as a background agent, Claude pulls all closed-lost deals from the last 7 days via a secure Hubspot AI integration. All context is provided, including: internal/external labels, stages, sources, owners, and team hierarchy. Instead of one agent doing everything (a costly time suck), the work is split across sub-agents to avoid a back and forth loop. One agent gets deals, one aggregates lost reasons, and one runs the analysis. At the end, she gets a cohesive summary on Slack with deals, reasons, and trends. 

2. AI Deal Hygiene 

Cadence: Scheduled Weekly 

The prompt reads: "Give me all the deals of every AE that needs cleanup." Claude pulls each Account Executive’s deals and checks against her defined parameters (close data wrong, stage drift, amount mismatch, etc.). Next, each AE receives a tailored Slack message with the necessary action. Her team receives evidence-based nudges. Managers no longer have to micromanage. Clients get the service they deserve. It’s a win-win-win.  

3. Analyze Gone Dark Deals HubSpot

Cadence: Ad hoc 

The Account Executive label deals as “Gone Dark,” with no extra information provided. Hila wants to understand the reasoning. In her words, "Just because people write ‘gone dark’ as the loss reason doesn't mean that's true." 

Did the AE stop responding? Did the prospect stop responding? Was it both or something else entirely? Claude pulls the deals, cross-references every engagement, and classifies the actual reason why. The reason for the loss has evidence now. There is no BI tool or analyst required. With a CSV file and Claude, the truth becomes clear in seconds. This information prompts action. 

4. Self-Service Pipeline and Forecasting for Finance 

Cadence: On-Demand 

She no longer needs to ever ask an AE to "send me the pipeline.” Instead, she built a role-specific HubSpot skills for finance that knows exactly what information to ask for. It interrogates the requester (time period, scope, pipelines), queries HubSpot, and returns an exportable CSV. 

As she explains, “"I taught it exactly what properties are important for bookings, for closed won, for open, and the Skill asks them, what's your time period, what's the scope, what are the pipelines, and then it pulls them the deals from HubSpot and makes an exportable CSV." She Vibe-coded a forecasting tool, canceled the SaaS they were using, and, “Now, we get to save $15,000 a year.” 

5. Subscription Management 

Cadence: On-Demand 

Rather than having to manually track subscription renewals for all of Agora’s clients, she taught Claude how to map the existing line items to the correct subscriptions, identify the missing renewals, and create the assumed auto-renewal records. 

Being able to update HubSpot records through an AI connector saved her countless hours of manual work. She shares, “That connector is also scoped specifically to me as an Operations user, since record-editing access is limited to only a select group of people.”

6. Pro Tip: The CSV Shortcut 

When she already knows the deal set, she exports a HubSpot list to CSV and uploads it, instead of making the agent crawl the CRM. "Claude reading a CSV file is so much more efficient than Claude going into HubSpot and trying to narrow down everything."

The Takeaway

Every critical workflow has been automated by giving the AI agent HubSpot access, securely. All results are pushed directly to Slack, removing the need for people to ask questions. The answers are already waiting. Best of all, every action is governed and traceable. 

The truth is that every department needs different levels of access in HubSpot. With a HubSpot connector, managers and leads can set up specific scopes for each respective team and said access will only apply to its relevant users. 

She’s a Sales Operations Llead that has indirectly transformed into a BI tool, coder, apps developer, all without ever having to write a line of code. As she says, "I'm trying to surface information to people without them having to look for it." Using a Claude HubSpot connector made it doable, easy, and scalable. 

Where it stalls (the honest part)

Using HubSpot AI automation for RevOps has real results. But, it doesn’t always go as planned.

Agents on HubSpot can break or get blocked. 

Here are a few lessons she learned (and shared), so you don’t have to learn the hard way: 

1. Reaching Limits 

This was a use case where Hila’s Hubspot MCP server was failing. Running daily, the connector was supposed to cross-reference three data sources: Avoma meetings from the last day, HubSpot emails, and a list of partner domain emails. If a meeting participant matches the partner domain, it is to log the AE/Customer/Partner trio and scan new-business deal emails for the partner domain activity. If the trio hadn’t been logged in 30 days, it is to push an alert to the Partnership Team’s Slack channel to take action. 

However, Hubspot returned “results too large” on a 7-day email pull. "It actually just failed. The HubSpot results are too large when I'm trying to look at the emails from the last seven days." Along with that constraint, the Avoma meetings are named by the AE, so there are naming inconsistencies. 

2. Choosing the Wrong Tool for the Job 

Bulk writes are not the right job for a HubSpot connector. Her team was using Claude to standardize hundreds of records to fix date formatting inconsistencies (US/EU data flip). Claude fixed the CSV file and then pushed updates to the HubSpot connector. But, it took hours and burned heavy token usage as it batched 10 records at a time. 

Instead, a direct CSV import to HubSpot could’ve taken 30 seconds. The connector is not the right tool for bulk writes. Had she had token visibility, she would’ve known this right away and been able to prevent wasting resources.  

3. Exposing Sensitive Data 

The connector may be the right key, but who you give the key to matters most. A single Hubspot API key exposes the entire CRM and marketing database to the AI agent. In this case, it is Claude. 

Nobody should be able to grant an agent organization-wide CRM access. It puts sensitive data at immense risk. In most cases, organization leaders don’t even know when it’s happening (this is the problem of Shadow AI). 

How to connect an AI agent to HubSpot safely

To connect AI agent to HubSpot securely, make sure it is per-user and per-object scope at runtime. Every action should be audited to a human. Every prompt should be behind a guardrail. 

Hila did it with Willow, and so can you. 

Willow is a robust Agentic Access Platform for every AI agent. It’s a control plane. Not a tool. Not an MCP gateway. 

With Willow, you get secure HubSpot AI integration: 

• Least privilege at runtime: The agent touches only the deals and contacts the rep already owns. 
• Scoped: Instead of giving the AI agent a blanket token with full access to read/write/delete, the agent is granted on-demand permission that is restricted. This makes it so it can only work on the specific prompt. Permissions expire once the job is done.  
• Secure architecture: People receive only the information they need, when they need it. To adjust access, manual permission is required. It is read-heavy by default (optimized for data consumption). It is write behind an approval guard (any data creation, deletion, or modification must be approved before it takes effect). 
• Auditable: Skills pulled from the Internet can carry API keys or prompt injection, leaving your entire organization vulnerable. The worst part is that this shadow AI can be running without anyone ever knowing. Willow provides a full audit trail of every action. And, every action is tied to a human user. 

With Willow, you can shrink the AI attack surface, adopt AI safely, at speed, and prove AI is actually working. 

Connect HubSpot the governed way 

Hila is the hero of this story. Want to be the hero in your organization?

Rev up your RevOps with a single click that leads to a scoped, audited, and security-approved HubSpot connector for your chosen AI agent. 

With Willow, you can make Monday mornings feel like Friday evenings.