Updates blog — Tuesday, June 23, 2026

HubSpot Updates: June 23, 2026

Seven updates landed June 23, and the center of gravity is agents. Three of them touch how agents connect, run, and hand off work: the Agent CLI, a new Actions Library for Customer Agent, and a clearer set of Customer Agent statuses in help desk. Around that sit an expanded catalog of buyer intent signals, a couple of quiet quality-of-life fixes, and one developer-platform change worth a calendar note.

If you watched the show, you already heard the conversation around four of these. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

HubSpot Agent CLI

The HubSpot Agent CLI brings your HubSpot data and intelligence into OpenAI Codex, Claude Cowork, and Claude Code, so agents can run repetitive, bulk, and scheduled work against your portal on a schedule rather than on demand. The example asks are squarely RevOps: find high-fit contacts with no deal and no recent activity and send a prioritized cleanup list, or pull a contact's last five tickets and flag recurring patterns. This moves to public beta after a run in private beta, which is the real news here.

Why it matters: This is the most strategically interesting release in the batch. HubSpot has been saying agents should be able to run on HubSpot and to run HubSpot, and the CLI is the second half of that. The shift to public beta widens access well beyond the early group, and it changes the admin job in the process. The work moves from doing the task to designing the recurring instruction and deciding what an agent gets to apply on its own versus what a human reviews first.

For the earlier breakdown from when this was in private beta, see our May 29 recap. For more details: HubSpot Agent CLI public beta.

Track 20 New Company News Signals in Buyer Intent

Buyer Intent's news signal catalog grew to twenty signals across four themes: financial moves like IPOs, earnings, and strategic investment; leadership changes like executive hires, departures, and retirements; corporate structure shifts like spinoffs and ended partnerships; and competitive or risk events like a competitor getting named, a lawsuit filed, or a client lost. Each signal carries its own detail, including company domain, summary, references, and the specifics behind it, and you can filter, segment, score, and trigger workflows off them. This is available to all customers with HubSpot credits.

Why it matters: The value is timing. A tracked account raising a round or losing the executive who championed you is a moment, and moments go stale fast. The thing to flag is restraint. These signals are a reason to enter a conversation, not a license to pitch off someone's funding announcement, and the teams that get value here will put a filter and a person between the signal and the outreach rather than automating straight off the trigger.

For more details: Track 20 new company news signals in Buyer Intent.

Managed Saved Email Templates

Saved email templates now have their own dedicated tab on the email listing page, so you can find and start from a template without digging. Nothing changes about how templates function; this is purely about where they live and how fast you can reach them. It is live across Marketing Hub Free, Starter, Professional, and Enterprise.

Why it matters: This is a findability fix, and findability is the kind of small efficiency that adds up across a team that builds a lot of email. The reach is the story. It lands on every Marketing Hub tier, including Free, so it is one of the few updates in this batch that touches nearly everyone.

For more details: Managed saved email templates.

New Actions Library for Customer Agent

The new Actions Library replaces the old single-form setup with a searchable, filterable catalog of pre-built CRM, workflow, and Shopify actions, organized by category. Customer Agent actions already existed; the new piece is the catalog, which removes the need to build and host API proxies or hand-wire every field to connect HubSpot CRM or a common integration like Shopify. This is in private beta, available across a broad list of hubs and tiers for portals using Customer Agent.

Why it matters: Pre-built actions lower the bar to get a Customer Agent doing useful work, which is the bar that has kept a lot of teams from reaching the resolution-rate gains the feature promises. One caution worth carrying in: out-of-the-box actions lean on native properties, so if your setup depends on custom properties, expect to do some wiring the catalog will not do for you.

For more details: New Actions Library for Customer Agent private beta.

Column Freezing for Pivot Tables

Pivot tables now default to frozen columns on both sides, the row labels on the left and the totals on the right, so scrolling horizontally keeps those reference points in view. It is in private beta across all hubs and tiers.

Why it matters: Wide pivot tables lose their meaning the moment you scroll and the labels disappear. This is a small readability fix, but it is the kind that removes a daily papercut for anyone who reads pivot tables for a living. Worth noting it is a human win specifically, since the people and agents reading your data do not scroll the way you do.

For more details: Column freezing for pivot tables private beta.

Customer Agent Status Property and Help Desk View Updates

The Customer Agent status property now uses a clearer set of structured statuses that show where a ticket sits in the agent-to-human handoff: Pending while the agent is handling it, Escalated when handoff has triggered but no human is assigned, Handed Off once a rep owns it, and None when the agent is not involved. The default help desk view now surfaces all agent-involved tickets sorted by urgency, with escalated tickets first. This moves to public beta for Service Hub Professional and Enterprise, with a Service Seat required.

Why it matters: As more Customer Agents run in help desk, the handoff is where ownership gets murky, and a ticket stuck between agent and human is a ticket nobody owns. Escalated is the status that earns its place, because handoff-triggered-but-unassigned is exactly where response times slip. The move to public beta means any qualifying Service Hub portal can put this visibility in front of managers now.

For the earlier coverage from when this was in private beta, see our May 29 recap. For more details: Customer Agent status property and help desk view updates public beta.

Sunset of Legacy Public App Creation

HubSpot has permanently turned off the ability to create new legacy public apps through the Developer Platform UI. New developer accounts lost it on May 26, 2026, and existing accounts lost it on June 23, 2026. New public app development now runs on HubSpot's Projects-based app platform. Existing legacy public apps are not affected and keep working as they are.

Why it matters: If you are not building public apps, this one does not change your day. If you are, the path forward is the Projects-based platform, which comes with CLI-based workflows, UI extensions, app cards, and better deployment tooling. This is part of the same developer-platform modernization that tightened marketplace listing requirements earlier this spring, and the direction is consistent: older app architecture is being retired in favor of the newer toolset.

For more details: Sunset of legacy public app creation.

Key Takeaways and Next Steps

Agents are getting more capable and more manageable at the same time: The Agent CLI and the Actions Library both lower the work it takes to put an agent on a real task, while the new Customer Agent statuses make the agent-to-human handoff something you can see and route. Capability and accountability are arriving together, which is the healthier version of this rollout. If you run Customer Agent, the status changes are worth turning on before you scale the agent further.

Credits are quietly the throughline: The buyer intent signals run on credits, and custom signals are heading toward pricing of their own. As more of HubSpot's most useful capabilities sit behind credit consumption, the cost of an automation becomes a design question, not just a tier question. Model what a signal-triggered workflow will cost before you turn it on at scale.

Match your effort to the update: Managed email templates and pivot table column freezing are small and live or nearly there, so use them and move on. The CLI is the one to invest real learning time in, while the public beta is open and the cost of experimenting is low.