If your team has ever hit a wall where the AI tool you're using just can't reach a certain part of HubSpot, you know how frustrating that is. You end up switching tabs, pulling in a developer, or building a custom connector just to do something that feels like it should be simple.
This update changes that equation in a meaningful way. It's one of the more practical AI releases HubSpot has shipped this cycle.
What This Update Actually Is
HubSpot's Agent CLI is a command-line interface that lets AI agents interact with your HubSpot portal. Think of it as the layer that sits between an AI assistant (like a Copilot or an internal agent you've built) and the actual data and actions inside your account.
Before this update, that CLI had a limited set of commands. It could handle some marketing tasks and a few other operations, but big chunks of HubSpot were off-limits without a separate connector or custom code.
With v0.17.0, HubSpot is enabling approximately 5,000 additional actions. These actions let AI agents retrieve information and make changes across a much wider surface area of your portal. Examples include creating marketing campaigns that go beyond the CLI's existing commands and pulling goals and forecast data without needing dedicated CLI commands.
One important caveat: what's actually available to your agents depends on your account's features and the permissions you grant during the setup process. Not every action works in every portal, and audit logs may not capture every change. HubSpot is transparent about this, and so are we.
Why HubSpot Shipped This
The external problem is straightforward: AI tools are only as useful as the actions they can actually take. If an agent can answer a question but can't reach the data or trigger the change, your team still has to do the manual work. That defeats the purpose.
The internal frustration is just as real. Humans who adopted AI tools early often find themselves stitching together workarounds because the integrations don't go deep enough. That creates tool overwhelm, not efficiency.
HubSpot's answer is to surface more of its own API surface area through the Agent CLI, so the AI tools your team already uses can reach more of your portal without you writing a single line of custom code. That's the real value here: depth without complexity.
How to Use It Step by Step
Before you do anything else, make sure you understand the confirmation requirement. Any action that changes or modifies live data must be confirmed by a human before the agent runs it. Don't skip that safeguard.
- Update the CLI to v0.17.0 or later by running hubspot upgrade in your terminal. This is required. The new actions don't exist in older versions.
- If you originally signed in using OAuth, re-authenticate by running hubspot auth login --force. This prompts you to review and grant the additional permissions the new actions require. Read what you're granting before you approve.
- Enable the feature inside the CLI. Once enabled, use the CLI to discover which new actions are available in your specific account. The list varies by portal features and permission scope.
- Review each action before assigning it to an agent. For read-only actions, the risk is low. For actions that write or modify data, treat confirmation prompts as mandatory, not optional.
- Start with low-risk retrieval tasks first. Pull campaign data, goals, or forecast information before you let agents write anything. Build trust in the setup before expanding scope.
- Check HubSpot's Agent CLI guide for the full update and sign-in instructions. The source for this update is the official HubSpot product update at app.hubspot.com/product-updates.
What It Touches in Your HubSpot Strategy
This update ripples outward further than it first appears. It's not just a developer tool. It changes what's possible for anyone building or managing AI-driven workflows inside HubSpot.
Marketing teams can now direct agents to create campaigns, pull performance data, and surface insights without leaving the AI tools they already use. That's real time saved on tasks that used to require portal access and manual clicks.
RevOps and sales leaders gain the ability to retrieve forecasting and goal data through agents. This matters most when you're building dashboards or briefings that pull from multiple data sources. We've seen this pattern repeatedly in portals where humans spend hours assembling reports that an agent could compile in minutes.
Key Takeaway
The Agent CLI's new action library is essentially a programmable bridge between your AI tools and HubSpot's data layer. The value compounds as you layer it into existing automation workflows and reporting stacks.
If you're already using HubSpot's customer agent tools, this update fits naturally into that ecosystem. You can pair agent-driven data retrieval from the CLI with the testing and configuration capabilities covered in HubSpot's customer agent tester update to build more reliable, auditable agent flows.
One area to watch carefully: audit logs. HubSpot explicitly states that audit logs may not capture every change made through these new actions. That's a real gap if you're in a regulated industry or if your team needs change history for compliance. Build your own confirmation and logging protocols on top of what HubSpot provides.
Key Takeaway
Audit logs may not track every agent-driven change. Build human confirmation steps and document your own change log until HubSpot closes that gap.
If you're thinking about how AI agents fit into a broader human-first strategy, the article on trajectory before speed in human-centered AI is worth reading alongside this update. The principle applies directly: set the direction yourself, then let the agent add speed.
Who Should Care Most
This update is relevant across every hub and tier, but some roles will feel the impact immediately.
- RevOps leaders who want agents to pull forecasting, goal, and pipeline data without building custom connectors for every reporting need.
- Marketing ops humans managing campaigns at scale who want agents to handle creation and retrieval tasks while the team focuses on strategy and messaging.
- Developers and solutions architects who've been building custom integrations to bridge gaps the CLI didn't cover. Those gaps are significantly smaller now.
- Agency teams and consultants managing multiple client portals who want to use AI agents for research, reporting, and campaign work without multiplying their manual effort.
- Growing companies on any tier that want to do more with smaller teams. This is one of the fastest ways to extend your team's reach without hiring.
George's Take
“Five thousand additional actions sounds like a developer announcement. It's not. It's a signal that HubSpot is serious about making AI agents genuinely useful for the humans who run portals every day, not just the engineers who build them.”
What I keep coming back to is the confirmation requirement. HubSpot built in a mandatory human review step for any action that changes data, and I think that's exactly right. The goal isn't to hand the keys to an agent and walk away. It's to let agents do the heavy lifting on retrieval and preparation while humans stay in control of what actually gets changed. That balance is what separates helpful automation from reckless automation. As you roll this out, treat the confirmation prompt as a feature, not friction.
If you want to go deeper on the question of when AI should act versus when humans need to stay in the loop, the guide on AI lead follow-up and human-first handoffs covers that thinking in a practical way.
If your team is ready to build agent-driven workflows into your HubSpot strategy but you're not sure where to start, let's talk. Book a strategy call with the Sidekick team and we'll map out exactly which actions make sense for your portal, your data, and your goals.
Frequently Asked Questions
What is the HubSpot Agent CLI and what does this update change?
The HubSpot Agent CLI is a command-line interface that lets AI agents interact with your HubSpot portal. The v0.17.0 update unlocks approximately 5,000 additional actions, allowing agents to retrieve data and make changes across a much wider range of portal features without custom integrations or developer support.
Do I need a specific HubSpot tier to use the new Agent CLI actions?
No. This update is available to all hubs and tiers. The specific actions available to your agents will depend on the features your account includes and the permissions you grant when you re-authenticate with the CLI.
Is it safe to let AI agents make changes in my HubSpot portal?
HubSpot requires human confirmation before any agent runs an action that changes or modifies live data. That safeguard is built in. However, audit logs may not capture every change, so teams in regulated industries should build their own documentation and confirmation protocols on top of the native controls.
How do I upgrade to the new HubSpot Agent CLI version?
Run hubspot upgrade in your terminal to update to v0.17.0 or later. If you signed in using OAuth, also run hubspot auth login --force to review and grant the additional permissions the new actions require. Both steps are necessary before the expanded action set becomes available.
What kinds of tasks can the new Agent CLI actions handle?
The new actions cover retrieval and modification tasks across a broad range of HubSpot features, including creating marketing campaigns beyond the CLI's existing commands and pulling goals and forecast data without dedicated CLI commands. What's available in your portal depends on your account features and granted permissions.
How is the HubSpot Agent CLI different from a standard HubSpot integration?
A standard integration typically requires custom code or a third-party connector to link an external tool to HubSpot. The Agent CLI exposes roughly 5,000 actions directly to AI agents without additional connectors, reducing the need for developer involvement and letting teams automate work inside the AI tools they already use.
