Show recap — Tuesday, July 21, 2026

Another Orange Morning Recap: July 21, 2026

A Tuesday, and for once it was just the two of us. Casey and Chris held down the show alone, with a standing invitation on the table: if you want to co-host, come fill out the be-a-guest page and jump on. What started as a quieter episode turned into the most ambitious segment the show has run, a live app build that got away from us in the best way and ended on the first cliffhanger in Another Orange Morning history.

Here is what we got into: why sequence tasks finally knowing about the deal they belong to is a bigger deal than it sounds, Breeze Assistant learning to create payment links and the permissions conversation that comes with it, cross-object filtering landing on index pages and quietly changing how you interrogate the CRM, a pricing API that says more about where HubSpot is heading than what it does, and the deep dive that ate the clock: describing an app in plain language and watching Breeze Builder deploy it live.

Tasks That Know Where They Belong

Sequence Task Associations

Tasks created by a sequence will now automatically associate with the contact's related records, companies, deals, and other objects, following the activity association settings you already have configured. Until now a sequence task linked only to the enrolled contact, which meant a rep had to associate the company or deal by hand, or more likely never did.

The honest thing about tasks is that they are easy to create and easy to lose. You make one to remember something, it drops out of sight, and by the time you find the task list again it has grown into a wall you do not want to look at. What changes that is not more tasks, it is putting the task in the flow of the work instead of a separate queue. A task that lives on the record you are already working, and that can retrigger a notification, is a task that actually gets done.

Why it matters: this connects to a thread the show keeps pulling. Once a task is associated to its company and deals, it becomes something you can filter a record list by, so an urgent task shows up next to the contact it belongs to rather than in a queue you have to remember to visit. One practical note: the settings live under Settings, Objects, Activities, which is not where most people think to look, and the same panel now holds email log and track settings plus email frequency controls for deliverability.

For more details: Sequence Task Associations.

Breeze Learns to Create Payment Links

Breeze Assistant Support for Payment Links Creation

A few weeks ago Breeze Assistant could send a payment link. Now it can create and manage them: describe the product, price, discount, and billing schedule and Breeze drafts a ready-to-use link, then handles the whole lifecycle, cloning, updating, toggling discount codes, rerouting confirmations, and activating or deleting, all by asking. Chris watched Breeze make an update on its own without even pausing to ask for approval, which is the assistant getting more capable and more decisive at the same time. Credit cards are the only payment method for now.

The interesting part is not the capability, it is the guardrails. The moment money enters the picture, the instinct is to keep users away from a tool that can spin up and clone payment links from a sentence. But Breeze can only do what the user already has permission to do. This does not hand anyone new power, it takes the manual clicking out of power they already had. Many of the people who feel risky doing this conversationally could already do it by hand, just slower and less consistently.

Why it matters: the work to do first is not turning Breeze off, it is getting your permissions and process and data model right, so the people who should create links can do it in a sentence and the people who should not, still cannot. When the alternative is a two-to-three-hour quote process, letting Breeze decide whether to clone, what to update, and what you did last time is a real amount of time back.

For more details: Breeze Assistant Support for Payment Links Creation.

Filtering Across the Data Model, On the Index Page

Cross-object Filtering on CRM Index Pages

You can now filter records on an index page using properties that live on their associated objects. Filter contacts by a deal property, companies by a ticket property, any primary record by its related object's data. The pain this removes is specific and familiar: you land on an index page, realize you need to reference an associated record, and have to switch over to segments to do it. Casey opened the filter panel live on the show and called it the big one of the day.

There are honest limits worth knowing. You can filter on one association at a time right now, so you cannot yet say company domain is this and deal stage is that in the same view. When you need to stack conditions the panel points you over to segments, which is a nice touch, because plenty of people never knew segments could do more and would have assumed the filtering was impossible. It is a beta, so give it a moment to switch on.

Why it matters: this is another step in a march the show has been tracking for weeks, the steady arrival of association-aware filtering that used to require building workarounds with custom properties just to expose an association ID. It only pays off if you have leaned into your data model, because a filter across associations is only as good as the associations you have built. The next wish, said out loud, is for Breeze to just build the index view for you.

For more details: Cross-object Filtering on CRM Index Pages.

A Pricing API, and What It Signals

Price Books Public API

Developers and partners can now create and manage Price Books through the public API: build and organize pricing catalogs, assign products and prices, and associate price books with deals, all without touching the HubSpot UI. It opens the door to automated catalog migrations, ongoing price syncing, and custom pricing workflows for teams whose pricing already lives in an ERP, a PIM, a CPQ, or a homegrown system.

The signal here is bigger than the feature. A year ago the HubSpot posture felt like get everything into HubSpot and stop using your other systems. This is the opposite. Your accountant is never going to work in HubSpot, and the win is not forcing them to, it is getting the systems they do use to share accurate data. That shift has come on in roughly the last six months, and it is hard not to read AI as the reason integration suddenly matters more than consolidation.

Why it matters: there is a quiet admission in the update copy. It calls maintaining price books by hand time-consuming, which is the polite way of saying it does not happen. The more manual a process is, the less likely it is being done at all, and that is the real AI ROI story, the complex work that never got done before because it was too painful for a human to keep up. Price books and CPQ have always been exactly that kind of work.

For more details: Price Books Public API.

The Deep Dive: Describe an App, Watch It Build

Describe an app, deploy it to your portal

This is the one Chris had been waiting all show to get to, and it earned the deep dive. Describe a custom app in plain language and Breeze Builder deploys a real app page into your portal, no developer and no code, reading your live data every time you open it using your own permissions. What changed in this update is small and useful: enrolled beta users now get a direct link straight to the builder.

The framing is the part worth keeping. Reports and dashboards are flexible, but they answer standard questions and stop short of the random custom need. A report is constrained to charts and tables; an app page can be any layout, cards, grids, side-by-side comparisons, a scrollable workspace, whatever fits how your team actually thinks. It pulls data from across the CRM, deals, contacts, tickets, custom objects, alongside narrative, in a single view. As Chris put it, a report is something you run; an app page is somewhere you go. A permanent place in your portal built for exactly one purpose.

So we built one, live. The prompt was a content calendar for the new HubSpot updates object, and Another Orange Morning too, and Breeze Builder went off to work, pulling live data from both the updates object and the Another Orange Morning series at once. That is the whole point in one demo: the context of the business is already in HubSpot, and this sits right next to it. It is an early, invite-only beta with rough edges, and vibe-coding a full app takes a minute, long enough that we ran out of clock. So it ended on a cliffhanger, the first in the show's history. The promise is to show what got built tomorrow, when Zach is with us, and to not touch it in the meantime even if it breaks.

The best idea came out of the build itself. Lead scoring is supposed to be a thermometer, coldest to hottest, but what people actually want is different: not what did this contact do, but who are my hottest leads today, and what should I do next. Every user wants that answer no matter their role or the time of day, and when the portal cannot give it, that is a reason they stop coming in. An app page that reads live data and answers exactly that question might be the surface that finally delivers it.

For more details: Describe an app, deploy it to your portal.

The Sign-Off

Our first ever cliffhanger, and a build to pay off tomorrow with Zach in the chair. 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.