Updates blog — Wednesday, June 24, 2026

HubSpot Updates: June 24, 2026

Eleven updates landed June 24, and two threads run through most of them. The first is connected data: seeing and acting on associated records from where you already work, and automating relationships across them. The second is consolidation, with AI customization moving onto fewer surfaces and the prospecting agent picking up another data source. Around those, a pair of sandbox improvements and some admin housekeeping round out the batch.

If you watched the show today, you already heard the conversation around six of these, including a long look at the Custom Assistants sunset. If you did not: Watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Inline Association Table

The inline association table lets you see and act on associated record data directly from any CRM index page, with quick filters across the associated records. It is in public beta across all hubs and tiers.

Why it matters: Cross-object questions are some of the most common questions in a CRM, and answering them has meant clicking into records one at a time or maintaining paired lists as a workaround. Which contacts have a deal closing next month, which companies have associations that need attention: those answers now sit on the index page where the work happens. One clarification worth keeping straight, since it comes up immediately: this surfaces and filters within the associated records, it does not yet filter the index itself by association. For our earlier look at this when it first reached public beta, see our May 29 recap.

For more details: inline association table public beta.

Sunset of Custom Assistants

Custom Assistants are being retired and folded into Breeze Projects. On July 13, 2026, every Custom Assistant in your account automatically becomes a Breeze Project, carrying over its instructions, knowledge, and chat history, so customization lives in one place inside Breeze. There is nothing to migrate by hand; HubSpot moves them for you. This affects a long list of tiers, from Starter through Enterprise across most hubs.

Why it matters: The pitch is one surface instead of two. Breeze Projects is where persistent context, organized workspaces, and team sharing come together, with access controls that a standalone assistant did not have. The date is the part to put on your calendar. The conversion is automatic, so no action is required, but if you have invested real configuration into a Custom Assistant, it is worth knowing exactly where it lands and confirming the carried-over instructions read the way you expect once it becomes a Project.

For more details: sunset of Custom Assistants moving to Breeze Projects.

Association Action Targeting for Associated Records

When you use association actions in workflows, you can now target the associated records of the enrolled record, not just the enrolled record itself. The example HubSpot gives: enroll deals when they reach closed won, then mark the decision-maker contacts on those deals as champions at the company. It is live across Professional and Enterprise tiers in Sales, Marketing, Service, Data, Smart CRM, Content, and Revenue Hub.

Why it matters: Plenty of relationship changes happen one record removed from the thing that triggered them. Before this, reflecting those changes meant a second workflow or a manual update. Targeting associated records in a single workflow closes that gap, and it is most useful for the operational, black-and-white updates: keeping billing and shipping contacts current, propagating a status across connected records. The judgment call updates, the ones where a role only sometimes changes, are the ones worth keeping a human hand on rather than automating end to end.

For more details: association action targeting for associated records.

Forms Analyze Tab

A new set of forms reports now lives directly in the forms Analyze tab, with AI-generated insights and recommendations, the ability to edit and save reports to your own custom dashboards, and the option to replace the default Analyze tab with a dashboard tailored to your needs. It is in public beta across all hubs and tiers.

Why it matters: The default Analyze tab rarely matches what a given team actually tracks, which is why so many people rebuild it elsewhere every time. Bringing flexible, AI-assisted reporting into the tab itself keeps performance monitoring in the same place as the work, and the save-to-dashboard piece means a report you tune once does not have to be reconstructed later. It reads as part of a broader pattern of reporting following people to the surfaces they already use rather than living off in a separate workspace.

For more details: Forms Analyze tab reports public beta.

AutoCapture Website Events

AutoCapture automatically tracks clicks on buttons, links, menu items, and other interactive elements across your website with no additional setup or code. Once your HubSpot tracking code is installed, it captures visitor interactions, and you can promote the most valuable ones into verified events for use across HubSpot's tools. It is available for the Enterprise Customer Platform.

Why it matters: The familiar problem this solves is the click you wish you had been tracking. Set up tracking after visitors start clicking and that earlier data is gone, which has meant a lot of conversations that end in "we can track it going forward." Capturing every clickable interaction from the moment the code is active means you are never starting from zero, and it gives you a complete behavioral record to build lead scores, segments, and automation on. The quieter benefit is discovery: you often do not know which interactions matter until you have the history to look back through.

For more details: AutoCapture website events.

Simplified User Creation and Invite Flow

The user creation and invite experience now combines what were previously several screens into a single page, where you add a new user, assign their seat, and set permissions in one step. This has moved from public beta to live, and it is available across all hubs and tiers.

Why it matters: Adding a new user used to mean walking through separate screens for the invite, the seat, and the permissions. Folding that into one page takes real time off admin onboarding. It is not a flashy update, but every admin who has ever set up a new hire knows the friction it removes, and now that it is fully live it is worth using by default. For our earlier coverage from when it was in public beta, see our May 21 recap.

For more details: simplified user creation and invite flow.

Prospecting Agent Suggests Contacts from Seamless

The prospecting agent already searched outside databases to find net-new contacts matching your personas. The new piece is a Seamless connection, joining the existing Apollo and ZoomInfo sources, so the agent can pull persona-matched people from another database, add them to your CRM, and draft outreach. It is available to customers enrolled in the prospecting agent public beta.

Why it matters: Finding people who fit your target personas but are not in your CRM yet is one of the oldest jobs in sales, and another enrichment source widens the pool the agent can pull from. The caution is the one that always travels with enrichment-driven outreach: the data is the easy part, and results depend on the strategy and content behind it. A persona-matched contact answered with generic outreach is still generic outreach, so plan to invest as much in how you talk to these people as in the tool that finds them.

For more details: prospecting agent contacts from Seamless.

FileUpload and FileViewer for UI Extensions

FileUpload and FileViewer are new UI extensions components that let developers add file upload and display to app cards. Files are stored in a per-app folder in HubSpot's file manager, and uploaded files can optionally be attached to CRM records. This is in public beta across all hubs and tiers.

Why it matters: Until now there was no native way to handle files inside a UI extension, which forced workarounds or pushed file interactions out of HubSpot entirely. For teams building app cards, this keeps file-dependent apps in context on the record, with proper drag-and-drop upload and a real viewer rather than the file-property approaches people improvised before. It is a developer-facing update, but the experiences it makes possible show up for everyday users on the record.

For more details: FileUpload and FileViewer for UI extensions public beta.

Instagram Collaborator Tagging

When publishing Instagram posts from HubSpot's social tools, you can now tag up to three collaborators, each of whom gets an invite to share the post on their own profile. This is in private beta for Marketing Hub Professional and Enterprise.

Why it matters: Collab posts appear on every tagged collaborator's profile, which extends reach to each of their audiences. Before this, using the feature meant leaving HubSpot to post directly in Instagram. Scheduling collab posts alongside the rest of your social content keeps the whole calendar in one place, which is the kind of small consolidation social teams feel every week.

For more details: Instagram collaborator tagging private beta.

Select Use Cases During Sandbox Creation

When creating a sandbox, you can now select one or more use cases describing how it will be used and give it a name. It is available across Enterprise tiers, including Smart CRM, Revenue, Marketing, Data, Content, Sales, and Service Hub.

Why it matters: Sandboxes drift into shared, undefined testing environments where conflicting work produces unreliable results. Naming a sandbox and stating its purpose upfront sets expectations for who should have access and what kinds of changes belong there. It is a small bit of structure, but for anyone running several sandboxes at once it is the difference between a deliberate testing environment and a free-for-all.

For more details: select use cases during sandbox creation.

Sandbox Support for Permission Sets

When you create a sandbox, your permission sets will soon copy over from production, each with its name, object-level scopes, and granular access logic across CRM, marketing, sales, commerce, service, automation, reporting, and account tools. This is in development for Enterprise tiers across Content, Sales, Service, Smart CRM, Revenue, Marketing, and Data Hub.

Why it matters: Permission sets define what each role can see and do, and without them in a sandbox, user acceptance testing cannot really start. You cannot assign a beta tester to the right permission set and validate the real end-user experience until you have rebuilt every access rule by hand, which is a lot of overhead repeated every time a sandbox is created. Copying permission sets in means a sandbox starts with the same access structure as production, so testing can begin right away. Worth tracking as it moves from in development toward release for anyone whose testing depends on accurate permissions.

For more details: sandbox support for permission sets in development.

Key Takeaways and Next Steps

Connected data keeps moving closer to where you work: The inline association table and association action targeting come at the same problem from two directions, seeing associated records on the index page and acting on them inside workflows. Between them, the cross-object questions that used to require clicking around or building extra automation are getting answerable and automatable in fewer steps. Start with the index page, since it is the one that helps the broadest set of users on day one.

AI customization is consolidating, and the calendar matters: Custom Assistants folding into Breeze Projects on July 13 is the clearest signal that HubSpot wants AI configuration living on one surface with real sharing and access controls. The migration is automatic, so the work is not in moving anything, it is in checking that your carried-over setup behaves the way you expect once it is a Project. The prospecting agent gaining Seamless fits the same direction of more capability concentrated in the agent layer.

Sandbox tooling is maturing for the people who actually run UAT: Use cases at creation and permission sets copied from production both target the same audience, the admins running real acceptance testing in complex portals. Neither is flashy, but together they make sandboxes more like a governed testing environment and less like a shared scratch space.