Updates blog — Thursday, June 18, 2026

HubSpot Updates: June 18, 2026

Five updates landed Thursday, and they cluster around the quiet machinery of a HubSpot portal: automation that finally chains the way you expect, reporting that takes fewer steps, notifications that route correctly, and sandboxes that copy more of your real setup. None of them is flashy. All of them remove a workaround.

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

Platform Updates Detailed

Use Records Created in a Workflow Later in the Workflow

When you create a record inside a workflow, you can now use that record and its properties in later actions. In a company workflow, for example, you can create a contact and then add it to a segment, or pull its properties into a task or a notification for your team, all without leaving the flow. This is in public beta for Smart CRM, Marketing, Sales, Service, and Data Hub Professional and Enterprise.

Why it matters: The old pattern was to build a second workflow whenever you wanted to act on a record you had just created, often with a unique association label as the only reliable way to reference the right one. Spreading a single process across multiple flows is exactly how automation logic becomes hard to maintain. Keeping the created record available in the same workflow lets you handle more cases in one place, and it matters more as agents and AI steps start acting on context the moment it exists. This is the kind of foundational fix that pays off quietly across every automation you build next.

For more details: Use records created in a workflow later in the workflow public beta.

New Formula Options in the Custom Report Builder

The Custom Report Builder now offers two guided ways to write formulas alongside the existing syntax approach. Conditional logic handles if-then-else cases through an interface rather than written syntax, and a summary measure builds an aggregation on a measure the same guided way. If deal amount is over a thousand, return high value, otherwise return low value, without hand-writing the formula. This is in public beta across Professional and Enterprise tiers for all hubs.

Why it matters: The real shift here is being able to handle reporting logic inside the report instead of creating a calculation property you do not otherwise need. A lot of portals carry tech debt from the opposite habit, where every bit of report logic became a new property. There is still a place for a property, like combining several integration-specific fields into one durable value. For one-off reporting cases, this keeps the logic where it belongs and your property count lower.

For more details: conditional logic and summary measure in the Custom Report Builder public beta.

Notifications That Take You to the Right Record Across All CRM Objects

At-mention notifications now link directly to the exact record where the mention happened, rather than routing you to a different associated record. Notification support is also expanding to more object types, including Appointments, Carts, Contracts, Courses, Listings, Marketing Events, Orders, Services, and Subscriptions, which now support mention, follow, and assigned notifications. This is in private beta for all hubs and tiers, with access opening to people who request it shortly.

Why it matters: Being sent to the wrong associated record created confusion and extra clicks at the exact moment you were trying to act quickly. Landing on the right record regardless of object type removes a small friction that added up across a busy day, and the broader object coverage closes real gaps for teams working outside the standard contact and deal objects. If your team operates in Subscriptions, Orders, or custom-adjacent objects, the expansion is the part to watch.

For more details: notifications across all CRM objects private beta.

Sandbox Creation Now Copies Team-Based CRM Views

When you create a sandbox, team-based and shared CRM views across contacts, companies, deals, tickets, and custom objects are now copied from production. Saved views define what reps see on the index page, which filters surface the right records, and how managers operationalize playbooks, so a sandbox without them does not reflect how a team actually uses HubSpot. This is in development across Enterprise tiers, including Commerce, Content, Marketing, Data, Sales, Service, and Smart CRM.

Why it matters: Recreating team views by hand every time you spin up a sandbox was tedious and easy to get wrong, and it meant your test environment never quite matched production. Starting a sandbox with the same view setup your team relies on makes user acceptance testing realistic, new-hire training accurate, and end-to-end validation trustworthy. It is one more piece of the slow, worthwhile project of bringing sandboxes to parity with production.

For more details: sandbox copies team-based CRM views in development.

Sandbox Creation Now Copies Automated Transactional Emails

Creating a sandbox will now copy automated transactional emails along with any workflows or segments that reference them, and Deploy to Production is supported for new transactional emails as well. This is in development for Enterprise customers, with testing available to those who have purchased the Transactional Email add-on.

Why it matters: If transactional emails run through your workflows, recreating them and their dependent assets by hand for every sandbox was real, repeated work. Copying them across, with the workflows and segments that depend on them, lets you test that whole path without rebuilding it first. It is a narrower update than the CRM views copy, but for teams leaning on transactional email it removes the same kind of setup tax.

For more details: sandbox copies automated transactional emails in development.

Key Takeaways and Next Steps

The theme is removing workarounds, not adding features: Four of these five exist to retire a workaround you have probably built, the second workflow, the unnecessary calculation property, the manual sandbox rebuild, the click-through to find the right record. When a release batch reads this way, the value is in auditing where you still run the old workaround and switching it off.

Sandbox parity is worth tracking deliberately: Two of these fill specific gaps in what a sandbox copies, and both are still in development. If you test in sandboxes, it is worth keeping a running sense of what currently copies over versus what does not, because the answer keeps changing and it determines how much you can trust a given test.