Show recap — Friday, June 19, 2026

Another Orange Morning Recap: June 19, 2026

Happy Friday, and a happy Juneteenth. This was the second show of the week, which meant twenty-three updates had stacked up across three release days since we last sat down together. Casey, Chris, and Madelyn Donovan worked through them at a Friday pace, with a quick laugh up top about Chris having been parked on a different portal earlier in the week and seeing a completely different set of cool things than everyone else.

Here is what we got into: a workflow change that fixes something that should always have been true, a payments feature one of us flagged as a trap, a run of notification improvements, the Revenue Hub rebrand and what actually changed underneath it, a Claude connector that can finally build a real quote, and Madelyn's horoscope segment, which is quietly turning into its own thing.

A Workflow Fix That Should Always Have Been True

Use Records Created in a Workflow Later in the Workflow

The first pick of the morning came from the side of the room that does not call itself the workflows side, and the appeal was simple: this is one of those updates that says something so obviously useful you assume it already worked that way. When you create a record inside a workflow now, you can use that record and its properties in later actions. Create a contact inside a company workflow, and you can add it to a segment and pull its properties into a task or a notification, all in the same flow.

The practical frustration this removes is the two-workflow workaround. Until now, doing anything with a record you just created usually meant building a second workflow and finding a way to reference back to the right record, often by leaning on a unique association label. The cleaner mental model that came up on air: the workflow itself becomes the association. The record was created here, so you already know which one you mean.

Why it matters: This is the same logic that made using AI outputs later in a workflow so useful, extended to records and structured data. As HubSpot moves toward an automation canvas where agents act on context the moment it exists, keeping newly created context inside the same flow stops being a convenience and starts being the point. There is a real debate worth having here, and we wanted George B. Thomas's take on it: he tends to favor more workflows that are each less complicated, and this update pulls in the other direction. Both can be right depending on how you maintain things.

The Payments Feature One of Us Called a Trap

Personalized Activation Journeys

Someone clocked this one as a trap before we even opened it, and the warning held up. Personalized Activation Journeys gives approved HubSpot Payments merchants a guided flow toward their first payment. The trap was the word merchant, which sent the whole table down a rabbit hole about who this actually serves. After some back and forth, the read settled: a merchant here is a normal HubSpot customer who happens to be taking payments through HubSpot, not a separate class of payment provider.

Why it matters: Plenty of approved merchants never run a first transaction because the path from approval to payment is unclear, and activation stalls. Automating the first payment artifact and giving people contextual examples is a reasonable way to close that gap. The terminology question is not just pedantry. When the language in a release does not match how any business describes itself, the feature gets harder to find and harder to recommend, and that came up more than once today.

A Lot of Notification Updates Lately

Two notification updates landed close together, and they belong in the same breath. The first improves at-mention notifications so they take you to the exact record where the mention happened, and expands notification support to more object types, including Appointments, Carts, Contracts, Courses, Listings, Marketing Events, Orders, Services, and Subscriptions. The rollout on that one slipped, with access opening to requesters early next week. The second reworks notification emails so the full context arrives in your inbox: six notification types now show enough that you can catch up from email alone and reply to mentions without clicking through.

Why it matters: The notification conversation we keep having with clients is about bringing new people into HubSpot from elsewhere in the organization. Their instinct is to ask for an email about everything, and the honest answer is that a hundred notifications a day is its own failure mode. The useful version of this is exactly what these updates aim at: when something is a true FYI, send people to the record; when action is needed, give them enough context to act without hunting. It also reads as another step in the HubSpot Anywhere idea from last year. They are no longer trying to keep everyone inside the product all day.

Rolling Back One Bad Integration Without Touching Everything Else

Integrations as a Source in Restore CRM Changes

This one reads like a list of everyone's current pain, written back to them. You can now select a specific connected app as the source when restoring a CRM change, which lets you roll back property changes from a marketplace app, a private app, or an MCP connector like Claude, without disturbing changes made by anything else. Before this, an integration writing bad data left admins with two bad options: run a broad restore that risked reverting unrelated work, or fix records by hand.

Why it matters: The three sources named in the release are the three sources causing the most data trouble right now: a misconfigured Salesforce sync, the new ease of building your own apps to do things, and AI writing to the CRM. Being able to scope a rollback to one connected app and leave the rest untouched is the kind of admin control that becomes necessary the moment more than one system has write access to your data. For Enterprise teams running several integrations, this is a real safety net.

Conditional Logic Comes to the Custom Report Builder

New Formula Options in the Custom Report Builder

The Custom Report Builder picked up two friendlier ways to write formulas beyond the existing syntax approach: conditional logic, which handles if-then-else cases through a guided interface, and a summary measure for building aggregations the same way. The example that made it click on air: if deal amount is over a thousand, show high value, otherwise show low value, without writing the syntax by hand. It is every calculation property you have ever built, except you do not have to build it ten times to get it right.

Why it matters: The quieter win is that you can do this inside the report rather than creating a property you do not actually need. That runs straight into a habit a lot of us have not unlearned yet. The instinct, when a report will not do what you want, is to go make a property and come back, and there is a mountain of tech debt across HubSpot portals tied to exactly that reflex. There is still a real time and place for a property, like combining three integration-specific fields into one. But for one-off reporting logic, keeping it in the report is the better move. We also lodged a small request with the product team, since AI is writing most of these release notes now: please stop using the acronym CRB out loud.

Sandboxes Keep Filling In the Gaps

Two sandbox updates are in development and worth knowing about if you test changes before production. Sandbox creation will now copy team-based and shared CRM views across contacts, companies, deals, tickets, and custom objects, and separately will copy automated transactional emails along with the workflows and segments that reference them. The CRM views one hit home, since one of us had a sandbox deployment recently where the views were a big part of the work and did not carry across.

Why it matters: A sandbox is only useful for realistic testing if it reflects how your team actually works, and saved views are a big part of that. The honest guidance for anyone working in a sandbox right now is to check what currently copies over versus what does not, because the list is still being filled in piece by piece. These are both in development, so treat them as coming rather than here.

Revenue Hub Is Here, and What Actually Changed Underneath It

Commerce Hub was renamed Revenue Hub earlier this week, and the question worth answering is whether anything changed beyond the name. The short version from the room: it is mostly a rebrand, but a meaningful one. The rename reframes a pile of objects, orders, deals, invoices, and subscriptions, around revenue management and reporting, and it lines up with the quote-to-cash experience HubSpot has been building toward, which closes the long-standing gaps around MRR, ARR, and revenue that no single system has handled cleanly before. Alongside the name change, real functionality graduated. Contracts moved toward general availability, and Price Books moved from private to public beta, so customers may be exposed to more than they were a week ago.

Two updates inside that story earned a closer look.

Migrate Existing Billing Into Revenue Hub Contracts

In private beta, this lets merchants move active billing contracts from a legacy system into HubSpot Revenue Hub contracts while preserving the original effective date and controlling when HubSpot starts billing. With Revenue Hub powering automated billing through contracts, the migration question becomes unavoidable for anyone moving in.

Why it matters: The point of this is to move billing without double-charging anyone or breaking historical continuity for finance and RevOps reporting. That is the unglamorous, high-stakes part of any billing migration, and getting it wrong is expensive. The release note also gave us a small thing to send back to the team: contracts is an official object and should be capitalized, and a source of truth that appears in quotation marks does not read like much of a source of truth.

Create Quotes and Analyze Revenue via the Claude Connector

This was the one both of us wanted to dig into. In private beta for Revenue Hub Professional and Enterprise, the HubSpot connector for Claude can now build and manage quotes and quote templates using a revenue-aware tool. It pulls line items from your deal, applies your branded templates, and follows your product rules, approval rules, and permissions. Claude also gets read access to core revenue objects, so you can analyze revenue data in the same conversation. To turn it on, reconnect your HubSpot account and enable the Manage Revenue Objects tool in the connector settings.

Why it matters: The earlier version produced a basic quote with none of the CPQ logic, approval flows, or template branding that makes a quote sendable. This version validates against CPQ rules, recalls and republishes as single steps, and respects the guardrails that keep a published quote clean. The bigger picture, and the harder part, is trust. There is a lot happening behind the scenes here, and the work is to put both your humans and your AI in a position to succeed before you ask a team to quote this way. Get that wrong and people will quietly go back to building a spreadsheet and sending that instead.

Turning an AEO Gap Into a Draft

Content Agent: Create a Blog Post From an AEO Recommendation

You can now generate an answer-engine-optimized blog post directly from a recommendation inside the AEO tool. The AEO tool shows where your brand is missing visibility in answer engines, and acting on that used to mean researching competitors, reading citation data, and writing from scratch. Now a recommendation becomes a ready-to-edit draft already structured for the gap it identified.

Why it matters: The appeal here is not letting AI write everything. It is the natural step from here is what you are missing to here is a specific way to close it. Even if you want a human writing the final piece, going straight from a visibility gap to a structured starting point removes the slowest part of acting on AEO insights. The thing to appreciate is that it makes the work easier while making it more contextual, rather than adding AI for its own sake.

HubSpot Horoscopes Becomes What's in the Cards

Madelyn's horoscope segment came back, and it has graduated from a bit into a small system. She built a pipeline for the planets, then scheduled their movement across signs in workflows through the end of the year, complete with delays for when each planet shifts. Her reason was refreshingly practical: she knew she would never have the motivation to redo it manually, so she set it up once to run on its own. Each week she generates a reading that ties the current sky to the product updates that fit thematically.

The segment had a funny meta moment. The Aries reading, the sign all three of us share, described leading with maturity, defining entry criteria, naming stages clearly, and movement with an audit trail, and pointed at Flexible Stages for journey and funnel reports as the relevant update. It was, almost word for word, a description of the per-planet workflows Madelyn had just built. She felt seen.

What is coming next is the visual layer. Madelyn wants custom cards that show where each planet is, how long it stays, and whether it is in retrograde, with a spinning animation if she can pull it off, and there was a plan to set up time next week to get the custom app card working. The segment may get a new name to match the direction. What's in the Cards is the early front-runner. On a week where one of us activated a few clients with their own custom UI cards built through Claude Code, the timing is right.

The Rest of the Updates

The full breakdowns of all twenty-three updates from this stretch are split across three updates blogs by release date. The June 16 releases, including the Revenue Hub cluster, are here: HubSpot Updates: June 16, 2026. The June 17 releases are here: HubSpot Updates: June 17, 2026. And the June 18 releases are here: HubSpot Updates: June 18, 2026.

The Sign-Off

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. Have an amazing Friday and a great weekend, and we will see you Monday for another Orange Morning.