Show recap — Thursday, July 23, 2026

Another Orange Morning Recap: July 23, 2026

Chris was out Thursday, which meant Casey Hawkins and her Thursday friend Trisha Merriam ran the whole show themselves, or as Casey put it, the wild, chaotic way. Fitting, because an episode that started as a routine walk through the product updates page ended with Casey building the one thing HubSpot had just told us it could not do, live, in about a minute.

Here is what we got into: lead rotation finally reaching the Lead object, a sandbox update Casey has personal history with, workflow templates showing up in the marketplace, a "sunset" that reads more like a fix, and the big one, Agent Hub landing in public beta the same day HubSpot's agents start counting credits.

Lead Rotation Comes to the Lead Object

First up, a private beta: the rotate record to owner action in lead-based workflows now supports distribution models, round robin, balanced, or random, plus user availability settings for lead assignment.

If that sounds familiar, it should. These distribution controls already existed for objects like tickets and contacts. The news is that the Lead object was left out, and now it is caught up. Balanced assigns the next lead to whoever has the fewest open leads, which is the option most teams reach for.

Casey went looking for one thing and did not find it: weighted distribution. When two reps share a territory and one is newer, teams often want a 60/40 split instead of an even one. That is not in here. Round robin, balanced, and random are all even by design. Hold that thought, because it comes back at the end of the show in a way neither of us saw coming.

Why it matters: If you route leads and you have been stuck doing it by hand or in a separate tool because the Lead object did not support real distribution, that gap just closed for the common cases. The even-split limit is real, but for most teams this is the setting they were waiting for.

For more details: lead object workflow rotation distribution.

Sandboxes Start Telling You What Actually Broke

Two sandbox items were on the page. The first, sandbox creation now copying team-based CRM views, Casey called self-explanatory and moved past. The second one she had feelings about.

Now live: when supported assets fail to copy during sandbox creation, the error tells you the specific reason, an unsupported asset type, a dependency that no longer exists in production, or a mix of both, along with what to do next. Casey ran straight into this a month or two ago, ended up meeting with the sandbox team about it, and got shown this exact improvement. Her case was a score tied to a workflow that would not copy from sandbox to production, and the old error gave her almost nothing to go on. She knows HubSpot well enough to untangle most of it, and even she got stuck.

The bigger picture: sandboxes went from fully disconnected to connected, which was a real step, and now the copy experience is getting the polish it needed. It is still not all the way there, especially for teams coming from Salesforce, where the sandbox setup is a known pain point. But clearer errors are the difference between a five minute fix and an afternoon of guessing.

Why it matters: Better error messages sound minor until you are the one staring at "something could not be mapped" with no idea why. If you build in sandboxes, this quietly gives you back time.

For more details: sandboxes clearer errors when assets fail to copy.

Workflow Templates Land in the Marketplace

The first of two major update tags today, and now live: workflow templates are available in the HubSpot Marketplace, pre-built patterns you can browse and drop in to start faster.

We poked at this one in real time, and it is worth setting expectations. When Casey went looking, the templates were not showing in the marketplace yet, which happens with same-day rollouts. Worth knowing too: the workflows tool has had templates for a while, so templates themselves are not new. The marketplace piece is what is new, and it raised a good question. If these live in the marketplace, could the community publish their own? Casey has copied a workflow from Ryan Gunn before and rebuilt it around copying UTMs. Picture that shared as a template other people can install.

Casey's honest read: after building workflows for about ten years, templates tend to slow her down, because she already knows what she wants and has to unwind someone else's version to get there. But that is not most people. If starting from a blank workflow stops you cold, a proven starting point is exactly the help you need.

Why it matters: This is aimed squarely at the person who opens the workflow builder and freezes. A library of patterns lowers that first step, and if the community angle opens up, the useful templates will not only come from HubSpot.

For more details: workflow templates in the marketplace.

A "Sunset" That Reads More Like a Fix

Casey likes to hit the sunsets, and this one confused both of us on the label. Starting today, the definitions for eleven marketing event properties, things like attendees, cancellations, start and end date, and event URL, are standardized, meaning their field types and validation rules are now fixed. Anything you already customized stays as it is, locked at its current state going forward.

The reason it matters lives in your integrations. Marketing event properties are the foundation apps like Zoom use to sync event data, and inconsistent definitions are where sync problems come from. Casey has hit exactly that with Zoom webinars being finicky about syncing, so if this is what fixes that, good. The part we kept circling: calling a standardization a sunset is a stretch. Nothing is really going away, something is getting locked down. But the outcome, steadier event syncing, is welcome.

Why it matters: If you run events through Zoom or another connected tool, standardized property definitions mean fewer formatting conflicts and more reliable syncing. The label is odd, the effect is a stable foundation.

For more details: standardized marketing event property definitions.

Agent Hub Arrives, and Casey Builds the Thing HubSpot Couldn't

Casey grouped the last three updates because they clearly belong together: Meet Agent Hub, Meet Agent Builder, and Breeze Assistant building inside Agent Builder, all public betas. Agent Hub carried the day's second major update tag, and it is the headline.

Agent Hub is one place to see every agent organized by the outcome it drives, attract, identify, engage, close, and serve, build new ones, and watch how your whole AI team is doing. The old path to agents ran through the marketplace. Now there is a dedicated agents menu item that used to be the AI menu, an agent marketplace with HubSpot's pre-built agents and some MCPs, and a build surface for custom agents and the new agentic automation. Casey noticed the timing out loud: this lands the same day a lot of HubSpot's agents stop being free and start consuming credits. Putting every agent in one place is also where you go to see what those credits are doing.

Then the show turned. Remember the weighted routing the Lead object update could not do? Casey asked Agent Hub to build it. Plain language, no careful prompting, route new leads 60 percent to Trisha and 40 percent to Casey. Agent Hub drafted a weighted lead routing agent, and when we opened the custom code to check the math, there it was, a math random check against 0.6 doing the split. The thing HubSpot had just said the native setting did not support got built anyway, in about a minute, by asking.

That is the moment the episode had been building toward, and it is worth sitting with. Casey and Trisha both talked about how big and disorienting this shift feels, and Trisha named the honest version of it, the old Charlie Brown teacher feeling when the words start blurring together. This is a real adjustment. But the payoff landed clean. As Casey put it, you probably already have the tools. You just have to ask. And she did not even ask in a fancy way.

Why it matters: Agent Hub is the front door for how HubSpot wants you to work with AI, and it arrives right as agents start metering. The lesson from the live build is bigger than any one feature. When the native setting has a limit, the agent layer can often close the gap for you, and you get there by describing what you want, not by hunting for a checkbox.

For more details: meet agent hub and the agent builder.

The Rest of Thursday's Updates

A handful of Thursday's releases did not come up on the show but are worth a scan: a bump to five searchable custom properties per object, per-user and per-team call recording settings, a customizable title card on CRM records, a smarter Slack CRM card with a Breeze summary, and cleanup automation that can now delete unused blog posts. Full breakdowns of the day's updates live on the feed: HubSpot Updates on Another Orange Morning.

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.