Show recap — Friday, September 4, 2026

Another Orange Morning Recap: September 4, 2026

Friday morning, two weeks out from Unbound, and the update board had six things on it. Chris Carolan and Madelyn Donovan worked through them ahead of a long weekend, and two of the six turned out to be telling the same story from opposite ends.

Here is what we got into: a sunset notice that reads like housekeeping and is not, a private beta that removes the oldest excuse for not connecting a system to HubSpot, a second look at dashboard color themes with a new set of eyes on it, the seat question hiding inside contracts and Breeze, and the week's HubSpot horoscopes.

A Sunset That Sets a Precedent

Sunsetting Ad Sequences and Ad Goals

Madelyn picked this one first, on the grounds that a sunset is a strange thing to be surprised by. HubSpot is removing the ability to create and manage Ad Sequences and Ad Goals in the Ads tool. The Create dropdown no longer offers goals, sequences are gone from the ad creation flow, and the management sections for both have been retired. Sequences already running will keep running, but they will not advance to the next stage.

The stated reason is the interesting part. HubSpot says it serves many customers who are short on time and want more guidance with less manual work, so it is shifting toward a more automated ad management experience. Read that sentence again and notice who it excludes, which is nobody. That is not a segment, that is the whole customer base.

Why it matters: Chris read this as a precedent rather than a feature removal, and the read holds up. HubSpot is full of sophisticated capabilities that only ever worked when one specific person in the org sat down and drove them by hand. The failure mode is familiar to anyone who has inherited a portal: that person is gone, the org is still paying for the thing they built, and nobody left knows how it works well enough to get value out of it. This is the first clear signal that the AI toolset is meant to absorb that category of work rather than let it sit stranded. If you have ad sequences running today, get what you need out of them and plan for the automated path.

For more details: the full update on Ad Sequences and Ad Goals.

HubSpot Can Now Go Get the Data Itself

Poll an API to Ingest and Automate Data from Any Tool

This was the one worth the most attention, and it is written in the driest possible language. You can now create custom events by polling an external API. HubSpot calls that API on a schedule you define and captures what comes back as custom event occurrences, up to a hundred new items per poll, deduplicated by a unique identifier you configure. It is a webhook in reverse. Instead of the external system pushing data into HubSpot, HubSpot reaches out and pulls.

Those events then behave like any other custom event. They trigger automation, feed reports, and segment or score records. Paired with the workflows builder in Agent Hub, that means your triggers are no longer limited to what happens to exist in the marketplace. It also quietly answers a long-running Data Hub question, because a real share of what teams currently buy Pro Data Hub and write custom coded actions to accomplish becomes reachable this way.

Why it matters: The conversation went past the feature and landed somewhere more useful, which is why systems went unconnected in the first place. It was almost never the API. It was that the ERP needs a company recorded one way and sales is selling to a different name for reasons that make sense inside the sales process, so IT says the systems cannot be connected without a data lake sitting between them. AI can do that transformation now. What it cannot do is decide what the names are supposed to be. That is still the people and the process, and that is still the hard part.

For more details: the full update on API polling and custom events.

Dashboard Color Themes, With New Eyes On It

Reporting Dashboard Color Themes

This one has been on the show before, which the site now makes findable. Chris pulled it up on anotherorangemorning.com mid-episode as a demonstration of the feed working the way it is supposed to, complete with the earlier segment clip and Zach Hussion's take from August still attached. Then Madelyn gave it a second reading.

The feature applies a color theme to an entire dashboard so every eligible report uses the same palette, without touching individual report settings. Madelyn's case for it is that this looks like a small update and is not one. Consistent color is how a reader recognizes which pipeline they are looking at, spots a trend without being told, and keeps their footing across a dashboard. One confusing data point can put an entire dashboard up for debate, and once that happens the work behind it stops counting.

Why it matters: Chris added the caution that consistent colors are not the same as a coherent story. If green means go in one place and high impact in another, the palette is consistent and the meaning is not. HubSpot has made it much less work to be intentional here. Being intentional is still on you, and it is worth planning the palette before you apply it.

For more details: the full update on dashboard color themes.

Contracts, Breeze, and the Seat Question

Revenue Context for Contracts in Breeze

Until now Breeze Assistant understood revenue through deals and pipeline, which is also how most of the surrounding tooling understands it. The contracts object carries more detail: not only what was sold but what was committed, and how that commitment changed over time. This makes Breeze contract aware, so it can answer questions like total contract value and how monthly recurring revenue is moving.

The show spent most of the segment on the confusion sitting next to it. A good deal of contracts functionality does require a Revenue Hub seat. Modeling your data into the contracts object does not, and that distinction starts to matter the moment you want to connect contracts data to anything else. The broader point Chris made is that we are close to a world where access to an object no longer requires a seat, and the tools built on top of it are where seats apply.

Why it matters: There is a real trap under this, and it showed up in the show's own Hubsessed work. Data brought over from Stripe or another billing system can look complete on the record and have no line items anywhere behind it, which means the moment you try to use it with any other part of HubSpot's architecture it does not hold. That is the difference between moving data across and connecting systems, and it is the kind of thing that only surfaces when you go to build the contract and the subscription line item is not there.

For more details: the full update on revenue context in Breeze.

Two Quieter Ones

The payments account public read API got a short pass. It is a new endpoint for retrieving a HubSpot account's payments status, including enrollment, eligibility and transaction capabilities. The practical value is for anyone building around payments who currently has to go through the UI to find out whether an account is even approved, and it fits the same shape as the polling update: fewer reasons a system has to stay unconnected.

The show also stopped on enhanced meeting and call transcription for Notetaker, mostly because of the word enhanced. What changed is higher quality transcription for both meetings and calls recorded with the native Notetaker, with improved multilingual handling now extended to calls as well as meetings. Expect more small updates in this shape. Calls and meetings were separated properly not long ago, and every tool feeding them has to be reconnected one at a time without anyone waking up to doubled or halved activity numbers.

Will It Breeze

The prompt this week was payments and audiences, with an open invitation for Breeze to flag anything that looked wrong. It came back with a genuine catch: the portal does not currently show Commerce Hub as a purchased product, which is a naming artifact rather than a data problem, because it is Revenue Hub now.

That is a small answer with a large lesson attached. If you are asking AI for help anywhere near Revenue Hub right now, a lot of the underlying labeling still says Commerce Hub, and the model gets tangled in exactly the same place the humans do. Breeze surfaced things the room was not aware of, and it also needed correcting, which is the right expectation to hold for it today.

The HubSpot Horoscopes

Madelyn's standing Friday segment closed the show. It is Virgo season, Mercury is in Virgo, and the reading for Virgo was three quiet precision upgrades: an invisible honeypot field on forms that quarantines bots before they reach the CRM, segment filter groups that can finally be named something other than Group 1, and calculated properties that can output enumeration values. None of the three will make an announcement. All three remove something that has been bothering somebody for years.

The horoscopes live at anotherorangemorning.com/hubspot-horoscope and refresh weekly. Word is they will be available in person at Unbound, alongside HubSpot tarot.

The Rest of Friday's Updates

Also on the board and not pulled forward: TikTok Smart Plus ad creation from inside HubSpot, the help desk board layout redesign, the payment links API, the Breeze knowledge base agent, the Data Studio data sources API and its file ingestion counterpart, the customer agent action that collects ticket and contact properties before a human handoff, and the expansion of native WhatsApp for marketers. Everything else that shipped is in the HubSpot updates feed.

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 next time.