Classic CRM Cards Are Gone, Workflows Close Another Gap, and Breeze Finds the Missing Lifecycle Stage

Another Orange Morning Recap: Monday, November 9, 2026

Friday's show did not air, so Monday came with a weekend's worth of releases waiting, and Chris was out. That left Joshua Oakes and me to carry the morning. We split the reading the way I do whenever Chris is away: I read what the update is, whoever is with me reads why it matters, and we work out the rest out loud.

Here is what we got into: a few minutes of Monday small talk, this week's office hours and the events page, then five updates from November 6 through this morning. A sunset that has already happened, two new run settings in the Agent Hub workflow builder, enrolling in sequences on behalf of other people, scheduling and logging from the mobile app, and charging a stored payment method through an API. We finished with a Will It Breeze on the Leadership lens, which I ran in our portal and in a client's.

Before the Updates: Monday Small Talk and This Week's Office Hours

We started with Monday itself, and Oakes and I do not approach it the same way. I like Mondays and tend to hit my panic zone somewhere between Tuesday afternoon and Wednesday afternoon. Oakes's schedule has flipped over the last few months, so meetings now pack the front of his week and the focused work gets pushed toward the end.

If you are planning your week, the events page on anotherorangemorning.com pulls in sessions from all over the HubSpot community, including the Hubsessed office hours that run every day. Today's is AI-Native Office Hours with Trisha Merriam and Nico. Nico is the first person I go to with an AI question, and now and then his answer goes right over my head, which is why I love having Trisha there to bring things back down to earth. The admin HUG is tomorrow and covers the CRM record redesign. I have a conflict, so I will be watching the recording.

Oakes is also hosting the Reporting and Dashboards office hours on Wednesdays with Madelyn. They get into the practical how-to of reports and dashboards in HubSpot, along with the pitfalls and the stakeholder situations that come with them. He was clear that the topics are a guide and not a gate: "come any day and whoever's on that day will be happy to give you their best answer or get you in touch with the person who might have a better answer too."

Five Updates After a Day Off the Air

Classic CRM Cards Sunset

This one has already happened. Classic CRM cards, the static, sidebar-only cards built with the CRM extensions API, entered deprecation on June 16, 2025, and were fully retired on October 31, 2026, nine days before we aired. They are replaced by interactive app cards built with React on the UI extensions framework, which support more CRM objects. New marketplace apps could not include classic cards after June, and existing apps had until the sunset date to migrate.

My read was that this is a note for marketplace developers more than for portal owners: "this has already happened. So if you haven't noticed it in the last week, it probably isn't affecting you." If the cards inside an app you use have changed over the last year or so, that is the reason.

Why it matters: Oakes took it somewhere useful. Customizing HubSpot has gotten far more accessible, through Claude and through Breeze, for a whole company, a team or one person. The sunset is aimed at app developers, but his reminder to listeners was that "you can be an app developer too just for your internal usage, for your own self or for your team or for your org." His advice: "Kick the tires. See what you can build. Ask Breeze for help. Ask Claude for help." React app cards are where the platform is pointing, so it is a good week to find out whether a tool you wish lived on the record sidebar is one you can build yourself.

For more details: Classic CRM Cards Sunset.

New Run Settings in the Agent Hub Workflow Builder

HubSpot keeps bringing functionality over from the legacy workflow tool to the new builder in Agent Hub, and this release adds two run settings to triggers. Exclusion criteria works like unenrollment and suppression lists did in the legacy tool: you set the criteria that either stop a run from starting or end one already in progress, for any trigger tied to an object. Merge settings let you decide whether a record runs in a workflow when it meets the criteria upon merging with another record. That setting used to exist only for contact workflows and now covers every object-based workflow that supports merging. It is in public beta and was scheduled for release today, which usually means going live, though the beta label is still on it. To find the builder, go to Agents in the nav, then Agent Hub, then Workflow. The new nav icons confused both of us, so the search bar got a workout.

Exclusion criteria is the bigger one for me, because it comes up on a regular basis. At Unbound, in one of Kyle's sessions, the advice was to start building in the new builder and not the old one. I told the friend sitting next to me that "the exclusion criteria was one of the reasons" I was not comfortable making it my first place to build. Oakes agreed with a tweak: "I agree with that statement that you quoted of Kyle if you insert the word try instead." He is still hitting places where the new and old builders are not at parity, and he has barely moved work over in the fifty-six days since Unbound. He is looking forward to parity because of what it could do to the ceiling of what HubSpot workflows can handle.

The merge question got a laugh of recognition. When Oakes is checking a workflow before turning it on and it asks whether to enroll records if they merge, he finds he can never work out the consequences: "I just can't usually say no." I had the same reaction: "I am so glad I'm not the only one."

Why it matters: every gap in parity is a reason someone stays in the old builder, and each one closed moves the line. These two settings let you automate for exactly the records you mean, and the merge setting now reaches beyond contacts.

For more details: New Run Settings in Agent Hub Workflows.

Sequence Enroll on Behalf of Others

This is the one from Friday that we never got to. I called it private beta on air, but the release panel lists it as public beta. Sales ops managers and executive assistants with the right permission can enroll contacts in a sequence on behalf of other users. Emails go out from the selected user's inbox, tasks land in that sender's queue, and replies and activities credit the right person. The release note includes a subhead we do not see often, Reason for development, which says manual workarounds do not scale and they block adoption.

Oakes noticed the list of roles leaves out a scenario he runs into frequently: an SDR or BDR who tees up an opportunity and hands it to an account manager. He would love that handoff to be a one-click or fully AI-backed operation, and he likes this as a first step because someone can enroll the contact "instead of cloning one million sequences" and leaving you with sequences you cannot report on or manage. He also raised a quirk: "enrolling in a sequence using a workflow is sales enterprise, right?" He thought so but was not certain it is gated that way.

I have been hearing about this need for years. "I've gotten complaints about this need many a times over the years, so happy to see it." It usually shows up as a less tech-savvy rep with a list saying "hey, Casey, can you just enroll these people in a sequence?" It sounds like an easy ask, and in practice I end up sending them a video, because the questions the enrollment screen asks can feel intimidating on a team that is not comfortable in HubSpot.

Why it matters: outreach that comes from the right sender, with replies landing with the person who owns the relationship, is how a sequence is supposed to work. Anyone who builds sequences for a team should keep an eye on this one as it leaves private beta.

For more details: Sequence Enroll on Behalf of Others.

Scheduling and Logging Meetings From the Mobile App

This one is live and was last updated on Friday, November 6. The HubSpot mobile app now has two ways to act without opening a record first. Tap Create Meeting on the home screen to schedule a meeting, or tap Create and then Activity to log a call, task and more, pick the activity, associate it with the right record and save it directly on that record.

Oakes opened the app on air: "I'm launching the HubSpot app for the first time in a long time to try this out live." His verdict: "I can confirm, does what the update says there." I am not the target user. "I've had the HubSpot app before. I don't even think I have it on my phone right now." The app has gained a lot of features, but it is still built for the sales rep out in the field. "I like going out and about during the day, but I'm not normally meeting clients and stuff" and logging meetings, so it never earned a spot on my phone.

Why it matters: until now, scheduling or logging on mobile meant opening a contact or deal first, then navigating to create. Reps can now book a meeting between calls or log a call right after it ends, which keeps the CRM current with less effort. For the people it was built for, that is a great value add.

For more details: Scheduling and Logging Meetings Made Easy on Mobile.

Pay Invoice With a Stored Payment Method API

This is a Commerce Hub update, which is usually Chris's territory, so I took it in his absence. Sellers, partners and workflows can now charge a buyer's stored payment method against an invoice through a public API, in private beta. Until now, every charge on a stored payment method needed a human admin to click through the HubSpot interface, with no programmatic path. The release note says that breaks automated dunning, usage-based billing close and agentic accounts receivable, which all hit a dead end at the last mile.

My shorthand: "So anytime we see API now, we know it means AI." Here is the example I gave on air. "if you are one of my clients, Oakes, I have a stored payment method for you." You agree to a new project on a call with me, I process the transcript afterward, and with HubSpot connected and this API enabled I can say "Claude, go ahead and charge that using Oakes's payment method." Before this, I would have had to go into HubSpot and run it myself.

Oakes read the why-it-matters note, and it had more flavor than most. "Put a little extra spice on it, which I feel like I had to honor."

Why it matters: this is one more example of the work itself changing hands. A recurring subscription or a project approved in conversation no longer needs a person standing at the last step.

For more details: Pay Invoice With a Stored Payment Method API.

The Rest of the Updates

We didn't get to everything from Friday through Monday. These shipped too, and each one has its own page: Convert Existing Custom Properties to Sensitive Data, your conversation history is now searchable in Breeze Assistant, AI Connector Access to Sensitive CRM Data, Customized Task Properties and Subtasks, selecting which CRM records to copy when creating a sandbox, snippets copied during sandbox creation, the redesigned Product Updates page and Email Variants.

Will It Breeze: Leadership, and the Number Behind the Number

Oakes picked the Leadership lens, the area that tends to bring the most miscommunication and the most confidence at once. I spun the wheel and ran it on my screen. The prompt: as a member of our leadership team using agentic automation, can you show the work behind the number across the last ninety days? Neither of us was sure what that would mean. Breeze asked which number to explain, which is the right instinct, and I told it leads. I also tried it in a client portal, where it asked the same question.

The answer in our portal was a good one. Breeze said "the evidence points to integration-driven audience growth, not yet a verified result of autonomous agent work." It pointed to an integration as the largest contribution, noted that many entrants have no lifecycle stage set, and reported that the qualification agent event source returned no records. In its words, "The report therefore shows how records entered the system, not proof that agentic automation created qualified demand." It covered August 11 through November 9, which is the ninety days we asked for.

Oakes gave the verdict, and he gave it as the person who always has to speak up. "I always am the one poking everybody's balloons with a needle," he said, but Breeze did its job: "It flagged something, and to be honest, something that automation could support, which is setting lifecycle stages." So the answer to Will It Breeze was yes, with the caveat that we had not set Breeze up for success.

My follow-up was the obvious next question: "how can we use agentic automation to increase lead volume?" The first thing it flagged was that most of our contacts have no lifecycle stage. That does not surprise me in this portal, but "in a normal portal, that would be a huge red, I would be freaking out if that's what came back in the client portal." The client portal gave some interesting results too, and that is the next prompt I will run there.

See the prompt and more: Will It Breeze.

The Close: Renewals, Claude Projects and the Last Mile

For the week ahead, I have two clients redoing their renewals flow, including how renewals get populated and how we report on renewal data. Two at once made me wonder whether it is the end of the year and people are projecting for next. I am especially looking forward to them because of a conversation with George at Friday's super admin office hours, where he helped me see how to use AI to get plans moving. I can make the plan; executing it is where I turn into a blocker.

Oakes has been wrestling with a setup that lets Claude work in client portals from the cloud, using the new projects feature, so the work keeps running if his computer goes to sleep. He hopes it lands this week and expects it to simplify his HubSpot work. The phrase from the payments update, dead ends at the last mile, came back as a joke while we were wrapping up, along with the Happy Monday bit.

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.