Updates blog — Wednesday, June 17, 2026

HubSpot Updates: June 17, 2026

Five updates landed Wednesday, and they spread across the platform rather than clustering: better notification emails, a guided path for new payments merchants, a more precise way to undo bad integration data, automated cleanup that finally deletes instead of archiving, and folders for the help desk sidebar. The through-line, if there is one, is control. Most of these hand an admin a sharper tool than the blunt one they had.

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

Platform Updates Detailed

Improved CRM Notifications in Email

Notification emails now carry the full contents of a notification, so you can get caught up without leaving your inbox. The new format covers six types: mentioned on a record, assigned a record, and stage, status, activity, or association updates on a record you follow. When you do want to dig in, a clear button and clickable card take you straight to the record. This is in private beta for all hubs and tiers.

Why it matters: A notification email used to tell you something happened without telling you enough to decide whether to act, which meant clicking through to HubSpot for context every time. Putting the full notification in the email lets you catch up from email alone on the road and reply to mentions without leaving it. Read alongside the broader push to meet people where they work, this is HubSpot conceding that not everyone needs to live inside the product all day, and building accordingly.

For more details: improved CRM notifications in email private beta.

Personalized Activation Journeys

Approved HubSpot Payments merchants now receive a personalized activation flow that guides them toward their first payment, automating the creation of a first payment artifact and offering contextual use-case examples. To be clear about the audience, a merchant here is a normal HubSpot customer taking payments through HubSpot, not a separate kind of payment provider. This is live across all hubs and tiers.

Why it matters: A lot of approved merchants never complete a first transaction because the path from approval to payment is unclear, and that stalls activation and long-term engagement. Meeting people at the point of approval with a guided next step is a sensible way to close that gap without manual hand-holding. For consultants, it also lowers the lift of getting a client from approved to actually collecting, which is usually where payments adoption stalls.

For more details: personalized activation journeys for HubSpot Payments merchants.

Integrations as a Source in Restore CRM Changes

You can now select a specific connected app as the source when restoring a CRM change, which lets you roll back property changes made by marketplace apps, private apps, and MCP connectors like the HubSpot connector for Claude, without affecting changes from any other source. Integration is now a named source type in the restore panel. This is available across Enterprise tiers, including Service, Sales, Content, Data, Marketing, Commerce, and Smart CRM.

Why it matters: When an integration writes bad data, a misconfigured Salesforce sync, a custom private app, or an AI connector, admins previously had to run a broad restore that risked reverting unrelated changes, or fix records by hand. Scoping a rollback to a single connected app and leaving everything else untouched is exactly the control that becomes necessary the moment more than one system can write to your CRM. The three named culprits, Salesforce, home-built apps, and AI, are the three writing the most data to portals right now, which is what makes this land.

For more details: integrations as a source in Restore CRM Changes public beta.

Cleanup Automation Deletes Unused Website and Landing Pages

Account Cleanup can now delete unused website and landing page drafts rather than archiving them indefinitely. Previously, cleanup archived identified clutter and moved it out of the main view, but stopped short of removing it, so fully clearing outdated content meant a second manual step of deleting the archived items. This is in public beta across Enterprise tiers, including Marketing, Content, Sales, Data, Service, and Smart CRM.

Why it matters: Archiving without deleting left the actual clutter in place and pushed the cleanup work back onto a person, which is how account cleanup quietly stops happening. Letting the automation finish the job removes that manual step and keeps content libraries from accumulating drafts nobody will ever publish. The usual caution applies to any delete automation: confirm what it is targeting before you let it run.

For more details: cleanup automation deletes unused website and landing pages public beta.

Introducing Folders for Help Desk Views

Folders give you a new way to organize views in the help desk sidebar. You can group related views into named folders to keep the sidebar structured and easy to navigate. This is live for Service Hub Professional and Enterprise, with a Service seat required.

Why it matters: The sidebar gets crowded as a team adds views to manage the support process, and an unorganized list means more scrolling and more clicks during the busiest moments. Folders are a small structural fix that keeps the right view findable when it counts. It is the narrowest update in this batch by audience, but for Service teams running a dozen-plus views, it is the kind of quiet quality-of-life change people notice every day.

For more details: folders for help desk views.

Key Takeaways and Next Steps

This batch is about precision over blunt tools: The restore update and the cleanup update both replace an all-or-nothing action with a scoped one. If you have been avoiding CRM restores because they reverted too much, or skipping account cleanup because archiving did not actually clear anything, both of those reasons just got weaker. Revisit the workflow you abandoned.

Notifications keep getting smarter, which raises the stakes on your data: Richer notification emails are useful in direct proportion to how clean the underlying records are. The better these get at surfacing context automatically, the more a stale association or a wrong owner shows up in someone's inbox as a confident, wrong message. Worth a look at what your team is actually receiving before you expand who gets notified.