Another Orange Morning Recap: May 14, 2026
The first official week back was supposed to ease into a rhythm. Instead, the show capped Thursday with five friends in the room, three updates pulled forward for discussion, a Will It Workflow that became its own commentary on where HubSpot is heading, and a private beta walkthrough from the HubSpot product team that closed out the hour.
Here is what we got into: two chat-adjacent updates from the May 13 release, a Will It Workflow segment that landed on a connected-email, line-item, send-for-review use case, and a guided tour of the Agentic Automation Builder ahead of next Tuesday's private beta opening.
The Friends Floodgates Opened
The cold open was about the show itself. Last week was just Casey and Chris all five days. This week, the friends are back. Thursday brought Trisha Merriam, Rylee Powell, Davis Mastin, and Becca Stamp into the room together, which Chris noted was the most friends the show has had on so far. It set the tone for the hour: more voices, more angles, more layering on the same updates.
Two Chat Updates, Same Question
Casey flagged the customer agent suggested questions update as the one she was most interested to discuss, and Chris agreed without coordinating first. The update moves suggested questions from a hover or page-overlay treatment into the chat surface itself, appearing below the agent greeting once a visitor opens the widget. The experience is cleaner, the prompts more useful in context.
What made the segment go deeper was Chris using the moment to set context for the rest of the show. With Davis and Becca on the line, Chris asked for an architecture-level read of how Breeze Assistant, the foundational HubSpot agents like customer agent and prospecting agent, and the soon-to-launch Breeze Studio custom agents all relate to each other. The conversation landed on a tiering: HubSpot-native and configured but not changeable, then the marketplace of HubSpot-built agents, then the fully custom agents coming through Breeze Studio. The word “agent” is doing a lot of work across the platform right now, and the show used the update as an excuse to slow down and name what is what.
The conversation then connected to the second chat update of the day: personalization token support in rules-based chatflow welcome messages. This one lets you insert tokens like first name or company name directly into the initial greeting, with default values rendering when a visitor is not recognized. The hosts got into the helpful-versus-creepy line, where a first-impression personalized hello can feel intrusive but a personalized greeting on the second or third visit feels like the company finally caught up. The takeaway from the conversation was that the right place for this is post-sale: customer portals, customer success rooms, the surfaces where the person has already given you the data and expects you to use it. The hosts also surfaced an open strategic question for portal owners: with this update, customer agent, and Breeze Assistant all overlapping in capability, which one do you actually deploy where? The shared answer was that it depends on the business, the use case, and where the determinism needs to live.
Will It Workflow: Line Item, Connected Email, Send For Review
The spin landed on line item as the object, connected email as the app, and send for review as the use case. The room agreed that line items have to be associated to a parent object that has an owner, and an owner likely has a connected email, which is the user-settings flag for whether their email is wired into HubSpot. The path Casey walked through was: when a line item changes, find the connected email of the parent record's owner, and route the record for review.
The interesting moment came partway through the build. Rylee surfaced the realization first: the workflow logic the room was assembling, the kind of detached, branching, “I might not know what object I am working with yet” pattern, was exactly what Davis and Becca were about to show off in the Agentic Automation Builder demo. Casey picked up the thread and ran with it. Half the workflows she has built over the years could be rethought. Half the workarounds her clients have lived with for years might not need to exist much longer. Chris named it directly: between the segment in progress and the demo coming next, there was a real chance some current client projects would need a fresh look.
Watch the episode for the full build and to see the workflow come together step by step.
Agentic Automation Builder: The Demo
Davis Mastin walked the room through the new automation builder, which goes into private beta on Tuesday, May 19 at 9 a.m. Eastern. Anyone currently using custom agents will be ungated automatically. Over the following month, access expands to everyone with custom agent access.
The visual change is immediate. A drag-and-drop canvas replaces the linear workflow tree, with hotkey controls and a feel closer to Canva or Lucidchart than to the legacy workflow builder. The structural change is bigger. Triggers no longer require selecting a single HubSpot object up front. The builder supports HubSpot CRM triggers organized by popularity, plus app events from third-party tools. Day one includes Google Sheets row triggers and one other connector. The point Davis came back to several times was that HubSpot does not want to care where the data starts. The flow can begin with a spreadsheet edit, a CRM property change, or an app event, and the steps that follow are independent of the trigger object.
The other shift worth naming is detethering. You can lay out a flow on the canvas without committing it to a publish path, sketch alternative branches alongside the active flow, and use the canvas as a planning surface as well as an execution surface. Sticky notes are not in the day-one build but are on the roadmap for this year. For consultants and admins who have been moving back and forth between HubSpot and Canva, Miro, or a whiteboard to plan workflow architecture, the implication is that the planning can now happen inside HubSpot, in context, in the same tool that ships the work.
Agentic steps are the third piece. You can drop a custom agent directly into a flow, modify it inline for that specific use case, and have the agent handle the unstructured part of the work while deterministic steps handle the rest. Becca framed it as a road metaphor: the deterministic steps are the paved road you know, and the agent is the off-road segment that can take unstructured input and still get you to the endpoint. The governance value for admins is that the deterministic steps stay deterministic, and the agentic steps are confined to the spaces where they help.
A few practical notes from the segment. Day-one action parity is not complete; the team is working on bringing more legacy workflow actions into the new builder through the summer, and they are also building net-new actions that will land in both surfaces. Existing workflows will migrate into the new canvas without rebuilding, with full data schema preserved. Breeze Assistant will be able to help decide whether something should be an agent, a workflow, or a workflow-with-agent, based on what you describe.
For more details: Agentic Automation Builder private beta
The Rest of May 13's Updates
Two updates from May 13 did not get pulled forward on the show: the SurveyMonkey integration that auto-attributes survey responses to HubSpot contacts without an extra email field, and the mobile list views update that brings the same properties from your desktop table views into the mobile app. Full breakdowns of all four updates from May 13 are on the updates blog.
The Sign-Off
You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.