What This Update Actually Is
HubSpot replaced the old single-form action setup inside Customer Agent with a proper Actions Library. It's a searchable, filterable catalog of pre-built actions organized by category: CRM, Workflows, Shopify, Commerce, Notes, and Custom API.
Before this shipped, connecting your Customer Agent to CRM data or Shopify required building and hosting API proxies, then wiring every field by hand. That's a developer task. Most Service Hub teams couldn't do it without help.
Now the catalog does that heavy lifting. You browse, configure, and publish. The custom API path is still there if you need it, but most teams won't.
Here's what's available right now in the library:
- CRM: Find, create, and update CRM objects; read contact and ticket properties; find associated records
- Workflows: Enroll a visitor or ticket in a workflow directly from a chat conversation
- Shopify: Find an order, search products
- Commerce: Find invoices, get a payment link
- Notes: Create notes on the conversation record automatically
- Custom API: Build your own action using the original configuration flow, still available for edge cases
Why HubSpot Shipped This
Customer Agent is only as useful as the data it can touch. An agent that can greet a visitor but can't look up their order, ticket, or invoice isn't resolving anything. It's just a chatbot with a fancier name.
HubSpot's own release notes state the goal plainly: lower the activation bar so more customers reach the resolution rate improvements that actions unlock. That's honest. Actions are the mechanism that turns Customer Agent from a deflection tool into an actual resolution engine.
The internal frustration this fixes is real. Humans running Service Hub portals know the gap. The AI agent is set up, the knowledge base is built, but the moment a visitor asks 'where's my order?' or 'can I get a payment link?', the agent hits a wall. Without actions wired to real systems, it can't answer.
The API proxy requirement was the wall. Most teams don't have the dev bandwidth to build and maintain proxies. The Actions Library removes that dependency entirely for the most common use cases.
How to Use It Step by Step
Setup is straightforward. Here's the exact path:
- Navigate to Service, then Customer Agent, then Train, then Actions.
- Click Add action or View all actions to open the full library.
- Browse by category or integration, or use the search bar to find a specific action by name.
- Preview how the action works and review example trigger phrases before committing.
- Click Continue to setup, fill in any required fields for your account, and publish.
One practical tip: review the example trigger phrases before you publish. These tell you exactly what a visitor would need to say to activate each action. If the phrases don't match how your actual customers phrase their questions, adjust your agent's training content to close the gap.
What It Touches in Your HubSpot Strategy
This update connects several parts of your portal that previously operated in silos. Let's walk through the ripple effects.
The Workflows action is especially significant. Customer Agent can now enroll a contact or ticket in a workflow mid-conversation. That means a support interaction can trigger an onboarding sequence, a win-back flow, or an escalation path, all without a human intervening. This pairs directly with the pattern we covered in our article on using records created in a workflow later in the same workflow. The two capabilities together let you build support automation that's genuinely end-to-end.
Key Takeaway
The Workflows action inside Actions Library means Customer Agent can now trigger automation, not just respond to questions. That turns every chat into a potential entry point for any workflow in your portal.
The CRM actions touch contact and ticket properties directly. An agent can now read a contact's lifecycle stage, find associated records, or create a new CRM object without a human doing it manually. That's a significant data hygiene win when it's configured correctly.
The Commerce actions (find invoices, get a payment link) matter most for companies using HubSpot's native commerce features. If you're running payments or subscriptions through HubSpot, your agent can now surface a payment link inside the conversation. That's a self-service resolution that previously required a rep.
On the Shopify side, the Find Order and Search Products actions are a foundational start. Ecommerce teams with Shopify connected can give customers real order status inside chat. More Shopify actions will likely follow as this moves out of beta.
Key Takeaway
Actions Library is one of the clearest signs yet that HubSpot's agentic strategy is moving from 'AI that talks' to 'AI that acts.' Every action you configure increases the resolution rate of your Customer Agent without adding headcount.
If you want deeper context on where this fits in HubSpot's broader AI roadmap, our pillar on the HubSpot agentic platform covers the full picture, including what's live, what's coming, and where the platform is genuinely heading.
Who Should Care Most
Not every team will feel this equally. Here's who this update matters to most:
- Service Hub admins who set up Customer Agent but stalled at actions because the API proxy requirement was too heavy. This unblocks you today.
- Ecommerce companies on Shopify who are already in HubSpot and want customers to self-serve order lookups and product searches without opening a ticket.
- RevOps and operations leaders who want to reduce ticket volume by giving Customer Agent real resolution capability, not just deflection scripts.
- Humans running HubSpot Commerce features who want the agent to surface invoices and payment links in context, cutting the back-and-forth between billing and customers.
- Portal admins on Service Hub Professional or Enterprise, Content Hub Professional or Enterprise, Marketing Hub Professional or Enterprise, Sales Hub Professional or Enterprise, Smart CRM Professional or Enterprise, or Data Hub Professional or Enterprise. This beta is broad. Check your account eligibility now.
Also worth noting: if you've already set up Customer Agent to respond to form submissions or to target specific contacts using lists, Actions Library is your next logical step. See how Customer Agent email targeting works with HubSpot Lists to layer those capabilities together effectively.
George's Take
We've seen this pattern across a lot of portals. Teams turn on Customer Agent, build a solid knowledge base, and then plateau. Resolution rates stay modest because the agent can only answer questions it already knows, not look things up, update records, or kick off a workflow. The Actions Library is the fix for that plateau. It's not a cosmetic change. It's the layer that makes Customer Agent actually useful for operational resolution, not just FAQ deflection. My strong advice: don't just add one action to check a box. Think through the five or six most common support conversations your team handles, map which actions would resolve each one, and configure those first. That's how you move the resolution rate needle in a meaningful way.
“The Actions Library isn't an enhancement to Customer Agent. It's the thing that makes Customer Agent worth having in the first place.”
If you're in the private beta and want to get this set up the right way, or if you're not sure whether your portal is structured to get real value from Customer Agent actions, let's talk. Our team has helped hundreds of HubSpot portals move from tool setup to actual results. Book a strategy call at sidekickstrategies.com and we'll help you figure out exactly where to start.
Frequently Asked Questions
What is the HubSpot Actions Library for Customer Agent?
The Actions Library is a searchable, filterable catalog of pre-built actions you can add to HubSpot's Customer Agent. It replaces the old single-form setup and includes CRM, Shopify, Workflow, Commerce, Notes, and Custom API action types. No API proxies or manual field wiring required for the pre-built options.
Do I need a developer to set up Customer Agent actions now?
Not for the pre-built actions in the library. HubSpot's new catalog lets admins browse, configure, and publish CRM, Shopify, and Commerce actions without building API proxies. The custom API option is still available for teams with unique integration needs that the pre-built actions don't cover.
Which HubSpot plans get the Actions Library?
The Actions Library is currently in private beta across Service Hub Professional and Enterprise, Marketing Hub Professional and Enterprise, Sales Hub Professional and Enterprise, Content Hub Professional and Enterprise, Smart CRM Professional and Enterprise, and Data Hub Professional and Enterprise. Check your account's product updates page to confirm access.
What Shopify actions can Customer Agent perform?
Right now, Customer Agent supports two Shopify actions: Find an Order and Search Products. These let the agent look up real order data and product information during a chat conversation without a human rep involved. More Shopify actions are likely to follow as the feature moves out of private beta.
How does the Workflow action in the Actions Library work?
The Workflow action lets Customer Agent enroll a contact or ticket in a HubSpot workflow mid-conversation. This means a support chat can trigger onboarding sequences, escalation flows, or win-back automations automatically, without a rep manually enrolling the record after the fact.
What's the difference between Customer Agent actions and a custom API integration?
Pre-built actions use HubSpot's own infrastructure to connect Customer Agent to CRM data, Shopify, and Commerce without any custom code. A custom API integration requires you to build and host an API proxy, then wire every field manually. The Actions Library removes that requirement for the most common use cases.
