HubSpot opens CRM doors to autonomous AI agents and sparks debate over trust and governance
HubSpot just made a move that will change how companies manage their customers.
The platform is opening up its APIs and its MCP server so that external AI agents can operate the CRM in a completely autonomous way — no human clicks needed, no dashboard navigation required, and no waiting for someone to type a command.
This is a major turning point.
For decades, software like HubSpot was designed for humans, with visual interfaces, menus, and buttons built to make life easier for anyone using a keyboard and mouse.
Now the logic is shifting.
AI agents do not need an interface — they call APIs, read structured data, and make decisions at machine speed.
And that is exactly the new model HubSpot wants to embrace.
Duncan Lennox, Chief Product and Technology Officer at HubSpot, published a post explaining the company’s vision for building an open ecosystem for the agent era. According to him, the company is continuously expanding its public API surface so that every platform capability, every workflow, every action, and every piece of context is accessible to the apps and agents built on top of it. No functionality should exist only behind a visual interface.
The promise is big: any action a human performs inside the platform, an agent will be able to do via API.
But along with that promise come questions the market still does not know how to answer properly.
Receive the best innovation content in your email.
All the news, tips, trends, and resources you're looking for, delivered to your inbox.
By subscribing to the newsletter, you agree to receive communications from Método Viral. We are committed to always protecting and respecting your privacy.
What happens when an agent makes a mistake?
Who is responsible when an AI deletes data, fires off incorrect communications, or makes decisions nobody authorized?
The tension between autonomy and control is at the heart of this movement, and understanding what HubSpot is building — and why it matters so much right now — is what this article will explore. 👇
What actually changed in HubSpot’s architecture
For years, integrating systems with HubSpot meant building connectors that mimicked human actions or relied on webhooks and pre-configured automations inside the platform itself. It worked, but it was limited. You could automate simple flows, move data between systems, and trigger notifications, but all of that required someone to have designed that path in advance — button by button, field by field. The agent did not decide anything; it just followed a script that a human had written.
What HubSpot is doing now is fundamentally different. By opening its APIs to AI agents and implementing the MCP server, the platform becomes an environment that can be operated directly by intelligent systems making contextual decisions in real time. This means an agent can enter the CRM, identify a lead who just interacted with a campaign, cross-reference that data with purchase history, assess the ideal moment for a follow-up, and execute that action without any human needing to approve each step of the process. The speed and precision of this model are incomparable to any traditional automation flow.
The MCP server — which stands for Model Context Protocol — is the protocol that allows language models like those used in modern AI agents to communicate with external systems in a standardized way. HubSpot adopted this protocol so that any compatible agent can connect to its ecosystem and operate with the same level of access a human user would have, but with the ability to process thousands of interactions simultaneously and without fatigue. It is a significant architectural shift, not just a product update. 🚀
According to Lennox, the platform’s APIs and MCP server are already live and come with ready-made connectors for Claude, ChatGPT, Gemini, and Copilot. Over 2,000 apps already run on the HubSpot ecosystem, and users are continuously creating new agents on top of the platform. The foundational layer of contacts, companies, deals, conversations, tickets, and activities is open and accessible to power integrations.
Context as a differentiator: the intelligence layer
One point that deserves special attention in HubSpot’s strategy is the understanding that the real AI race is not about language models or the amount of data — it is about context. Lennox was pretty direct about this: access alone is not enough. An agent that only reasons over raw records has no way of knowing what is normal for a specific business or what has worked for hundreds of thousands of similar companies.
And that is where the intelligence layer the company is building comes in. This layer brings together the insights companies get from the platform that help inform decisions — like lead scores, performance assessments, and market benchmarks — along with actions that drive concrete results, like qualifying leads, resolving support tickets, and saving deals that were about to be lost.
When an AI agent has access to this kind of contextual intelligence, it is not just executing tasks mechanically. It is operating with a deeper understanding of the customer’s history, behavioral patterns, and performance benchmarks, which can significantly improve personalization and responsiveness in every interaction.
HubSpot already offers its own internal agents called Breeze, which perform this type of work inside the platform. The next step, according to Lennox, is to make that intelligence available wherever teams and agents operate — inside or outside HubSpot. This means the company is moving toward a model where its Breeze agents and third-party agents can share the same contextual intelligence base fed by data from more than 280,000 platform customers. 📊
Why agent autonomy matters so much for CRM
The CRM has always been the heart of commercial operations for companies that take relationship management seriously. It holds customer data, interaction history, sales opportunities, support tickets, and much more. The problem is that all that data richness has always depended on humans to be activated intelligently — and humans have obvious limitations in time, attention, and scale. A salesperson can follow up with dozens of leads with quality. An AI agent with access to the CRM via API can follow up with thousands at the same time, with the same level of personalization for each one.
The autonomy that HubSpot is offering agents is what turns that capability into something operationally real. It is not just about having access to data. It is about being able to act on that data without friction. An autonomous agent connected to the CRM can update records, create tasks, send personalized emails, segment lists, qualify leads based on dynamic criteria, and even proactively reschedule meetings. All of this in response to events happening in real time — like a website visit, an email reply, or a change in the customer profile. That level of reactivity is what sets a modern sales operation apart from one still living on spreadsheets and manual reminders.
The company’s vision is clear and ambitious. Lennox described the end goal with two statements that sum up the magnitude of the bet: agents can run on HubSpot, and agents can run HubSpot. The difference between those two ideas is subtle but enormous. Running on HubSpot means any AI agent can gain a dynamic understanding of the business, informed by patterns observed across the platform’s customer network. Running HubSpot means agents will be able to operate the platform end to end — through APIs, the MCP server, the CLI, and potentially other access methods that emerge as agent technology evolves.
The practical impact goes beyond operational efficiency. When an AI agent operates with autonomy inside the CRM, it also starts generating data about the sales process itself that was previously invisible. Every decision the agent makes, every action it executes, and every result it produces can be logged and analyzed. This creates a continuous improvement loop that is much faster than any human feedback cycle. Companies that figure out how to use this will have a real competitive advantage — and that is no exaggeration at all.
The side nobody wants to talk about: risks of autonomy without control
All this autonomy comes at a cost that needs to be discussed honestly. When a human makes a mistake inside the CRM, the error is usually localized and reversible. They deleted the wrong contact, sent an email to the wrong list, updated a field with the wrong information. Annoying, sure. But manageable. When an autonomous AI agent makes a mistake, the scale of the error can be entirely different. Within seconds, it could have sent an incorrect campaign to the entire customer base, deleted records in bulk, or made business decisions based on corrupted data that no human ever reviewed.
And these are not hypothetical scenarios. The original article cites two recent incidents that illustrate the risks involved quite well. An AI agent powered by Claude, operating inside the Cursor tool, deleted PocketOS’s entire database in just nine seconds — including the backups. In another case, a security flaw at Vercel gave hackers access to customer API keys, showing how access tokens can be exploited when AI systems are granted overly broad permissions. Both episodes have already raised red flags across the industry about the limits of what happens when AI agents receive access without proper safeguards. ⚠️
The question of accountability is another point the market is still trying to figure out. If an AI agent connected via API to HubSpot’s platform makes a decision that causes harm to a customer or a business partner, who is liable? The company that configured the agent? The language model provider? HubSpot for opening the access? These questions do not have simple answers, and the regulatory environment around AI is still in its early stages when it comes to offering clear guidelines on this. For now, the responsibility falls on whoever decides to implement these systems, which puts enormous weight on the technology teams and leadership at companies that will adopt this integration.
What HubSpot can and should do — and what any company adopting this model should demand — is the implementation of robust governance layers. This includes detailed logs of every action executed by AI agents, well-defined permission limits so agents cannot execute critical actions without human approval, automatic alerts for out-of-pattern behavior, and rollback mechanisms to reverse actions in case of errors. Autonomy without these safeguards is not a competitive advantage — it is unnecessary exposure to risks that can compromise years of customer relationships.
How HubSpot positions itself against the competition
HubSpot’s approach goes further than most of its direct competitors. Companies like Salesforce and Microsoft are also introducing agentic frameworks and expanding API access, but they are maintaining tighter controls over how far those agents can operate within core systems. In those cases, agent activity is generally confined to pre-defined workflows, permission layers, and well-delineated governance models rather than extending to full operational control of the platform.
HubSpot’s ambition of achieving full API parity — meaning everything that can be done through the visual interface can be done programmatically — signals a much more expansive vision of autonomy. This distinction is what makes it essential for customer experience teams to maintain visibility and control over systems that are increasingly acting on their behalf, operating on critical data and processes that directly impact the customer relationship.
The company’s philosophy is that customers should be able to choose the best agents, integrations, and partners for their needs, even if they come from outside the platform. HubSpot’s intelligence should reach users wherever they work — inside or outside the platform, directly or through apps and agents built on top of it. It is an open ecosystem proposition that differs from the more closed model some competitors tend to adopt.
Trust and governance as core infrastructure
Lennox acknowledged that not all platforms will react to the rise of AI agents in the same way. Some will restrict access to their systems and prioritize control over interoperability. HubSpot believes the moment calls for the opposite. When agents can access data, act on behalf of customers, and execute business processes, openness and trust matter more than ever.
The company is treating trust and governance as core infrastructure — not as secondary features. According to Lennox, when a customer connects a partner tool, activates an agent, or builds something custom, they should know exactly what that component can access and what it is doing. Agents that act on your behalf are only useful if you can trust them.
This trust issue will become even more complex as autonomous agents take on customer-facing tasks. When multiple agents, integrations, and automated workflows begin interacting within the same environment, orchestration turns into a significant operational challenge. Any company that does not think about this seriously from the start will face problems that are much harder to fix once they are already in production.
What to expect from the market’s next moves
HubSpot’s decision will not stay isolated for long. Salesforce, Pipedrive, Zoho, and other CRM market players are already in similar races to make their platforms compatible with autonomous AI agents. MCP is being adopted quickly as the standard for communication between models and external systems, which means interoperability across different platforms and different agents will grow at an accelerated pace over the coming months. The ecosystem of tools around this — like agent orchestration frameworks, monitoring systems, and AI governance platforms — will also develop rapidly to keep up with this demand.
For companies using HubSpot today, now is the time to explore carefully and without unnecessary rush. Opening up APIs to AI agents is a real opportunity to gain efficiency and scale in commercial operations, but taking advantage of that opportunity well requires planning. Knowing which processes make sense to delegate to an autonomous agent, which ones require constant human oversight, and which ones are not yet mature enough for this transition is a strategic exercise every organization needs to work through in its own way — considering its context, its risk appetite, and the maturity of its technical team.
Rich, structured business context creates real opportunities to improve the quality and consistency of customer experiences. But that same richness, when operated by multiple agents without proper orchestration, can generate conflicts, duplications, and unexpected behaviors that hurt more than they help.
What is clear is that the line between software as a tool and software as a collaborator is being redrawn right now, and HubSpot is going all in on this direction. AI agents with autonomous access via API to the CRM are no longer science fiction or a lab concept. They are arriving in real commercial operations, with all the benefits and all the challenges that brings. And whoever understands this sooner will be better positioned to navigate this new landscape. 🤖
