Show recap — Friday, August 21, 2026

Another Orange Morning Recap: August 21, 2026

Friday, and the first thing on the table was the week itself. Chris Carolan opened the show with Casey Hawkins and Madelyn Donovan, and the first two minutes went to how strange time had felt for five days running: hope on Monday, a slow slide through Wednesday, and a Thursday-afternoon shrug that carries you the rest of the way. Then the list, six in a row, rapid fire.

Here is what we got into: a property beta that got pulled back before anyone could finish praising it, merged records finally keeping their ID, a cleanup automation demo that went further than the table expected, one-tap recording for reps standing in somebody's driveway, Knowledge Base Agent and the credit meter that starts running on September 16, and Madelyn's horoscopes to send everyone into the weekend.

The Dropdown Beta Got Rolled Back

Convert a text property to a dropdown property

The beta that converts an existing text property into a dropdown was first on the list, and it started as a compliment. Chris was building toward why it was a big deal, what it says about what HubSpot can now do to a property in place, when Casey cut in and told him to read the update itself first.

The note underneath was a rollback. HubSpot is temporarily rolling the beta back to make adjustments before trying again with a version adapted to recent feedback. Accounts return to the previous experience, no action is required, and any property already migrated keeps working as a dropdown. "Thank you for stopping me," Chris said.

The read in the room was that something actually came apart. A rollback at this stage usually means reporting or an audit trail broke in at least one customer platform, because pulling a beta back is not a small move. The counterweight arrived right behind it: HubSpot acts on beta feedback fast, and the note says there is a path forward. Then came the question anyone sitting on a half-migrated property is already asking. "Can I just keep the half-broken one? I won't complain that much about it."

Why it matters: if you converted a property during the beta, you keep it and it keeps behaving like a dropdown. If you were waiting to try it, you are back on the previous experience with nothing to undo. The thing worth watching is the second attempt, because a beta that gets pulled and reshaped tends to come back with its sharpest edge filed down, and the sharp edge here was converting a live property with live data already sitting in it.

For more details: read our take on converting a text property to a dropdown.

A Merged Record Keeps Its ID Now

Primary ID Preservation for Merged Records

This one carries the major update tag and earns it. When you merge two CRM records, HubSpot now preserves the primary record's ID as the surviving record ID. No new ID is generated. The secondary record's ID becomes a forward reference that resolves to the primary record ID.

Until now, every merge minted a brand new record ID. Integrations that cached or referenced record IDs broke without saying so. Webhook consumers received an unexpected object created event for what was conceptually the same record. Teams storing HubSpot IDs in outside systems had to go chase down the new canonical ID by hand after every merge. The room's reaction to that last line was that most teams never got that far, because the behavior was enough to talk them out of building the integration in the first place. A record you already identified being handed a new identity is the kind of thing that does not happen in other systems.

The best part of the segment was how recently the table learned the old behavior existed at all. The record URL has always redirected after a merge, which makes it very easy to assume the ID underneath rode along with it. Chris found out otherwise less than a month ago, running a merge through the MCP. "Claude actually was like, just a heads up. Now these records have different IDs. And I was like, I'm sorry, what?" It connected back to a client conversation from earlier in the week about wanting the record's own URL available as a property rather than just the record ID, and the answer landing here is close to the same shape: the old address resolves to the current one instead of pointing at nothing.

Why it matters: every failure this closes was a quiet one, which is exactly why so few teams ever traced the symptom back to a merge. If you have an integration caching HubSpot IDs, a warehouse keyed on them, or a webhook consumer that has been creating a second row every time somebody cleans up duplicates, this change stops that without any work on your side. And if you have been avoiding the merge button in a portal with integrations hanging off it, that reason is gone.

For more details: read our take on Primary ID Preservation for Merged Records.

Cleanup Automation Comes for Your Email Drafts

Cleanup automation now deletes unused marketing emails

Account cleanup can now delete unused marketing email drafts instead of archiving them indefinitely, and a recently deleted section holds what it removed for up to ninety days. Enterprise. The reason it matters is the step nobody was taking: cleanup archived the clutter, moved it out of the primary view, and then left the actual deletion to you as manual work. As the table put it, look at the number of tabs anyone has open at any given moment and you can guess how often that second step happened.

The first concern was templates. Plenty of teams clone an old email as a working template, because cloning carries the suppression list and everything else attached to it in a way the templates tool does not. Would cleanup know the difference and start nominating those every time? The answer on the page is customizable filters, which puts the weight back on naming conventions. There is a real win hiding in that too: an email worth keeping rarely still has "new email" sitting in the title field, so the low-value filter catches a lot on the name alone. And the honest line about the whole category came out early, aimed at the phrase "automation to immediately delete low-value unused email drafts." "Feels kind of like a dig, doesn't it?"

Then the demo did its own talking. Thirty-one emails in Casey's demo portal met the criteria, most of them from January and February, which she noted looks a lot like what shows up in production portals too. She went in to see what cadence options the automation offered, expecting another screen. "Oh, never mind. That worked better than I thought. Good thing this is the demo portal." It ran. The good news for everyone watching is that it archived rather than deleted, because the delete side is still gated behind a request under review, and the whole table landed in the same place at the same moment: "Careful with that, everybody." The expectation going in had been another check, and the assumption on the way out was that HubSpot will add the type-it-in-all-caps confirmation before delete ships for real.

Why it matters: this is Enterprise, and it is the difference between a cleanup tool that finishes the job and one that moves your clutter to a different shelf. Set your filters before you set the automation, because the tool is only as good as the criteria it matches on, and an automation that surfaces your templates every run is one you will stop opening. If you build a working template by cloning, give it a name that says so.

For more details: read our take on Cleanup Automation deleting unused marketing emails.

One Tap, and the Rep Is Already Recording

[Android] One Tap Mobile Notetaker and Meeting Review Enhancements

HubSpot mobile users can start recording an in-person meeting, or capture a post-meeting voice memo, with one tap from the home screen, without first creating or locating a CRM engagement. Reps can record while offline and associate the recording with the right meeting and CRM records once they are back on a connection. A review and action tab lets them read the AI summary, generate a follow-up email, replay the recording and transcript, and accept or reject suggested CRM property updates from the phone. Professional and Enterprise, public beta. Access to suggested tasks and CRM updates in the action tab requires joining the Notetaker with smart deal progression public beta.

The segment went straight at adoption. It is one thing for an admin to tell a sales team to download the app and record their meetings. It is another for a rep standing on a customer's porch to say hold on one minute while they find the right record and confirm an email address. The ones already using these tools have the app open before they knock. Everybody else has a reason not to, and the reason was always the setup, not the recording.

The offline half drew the strongest reaction, and it came out of real build experience: shipping a field app on top of HubSpot and hitting the same wall every time, which is what a rep is supposed to do when there is no internet and the job still has to get done. The requirements to support that are not small. Deferred association covers the other version of the same problem, the week where somebody records every meeting and something in the chain quietly does not connect.

The last beat was about admins, and it was a fair one. There is no reason for an admin to be fluent in the mobile app, because an admin is always at a desktop where they know the navigation cold. Which means the only way to get the mobile rollout right is to walk it yourself in the rep's shoes, and to stop assuming anything about what is installed on their phone. The show pulled up the iOS version of the same release to compare, and the screenshots matched, which is usually how it goes when the two ship together.

Why it matters: this is the update that removes the excuse. The recording was never the hard part for a field rep. Finding the record before the handshake was. If Notetaker adoption stalled on your team, it is worth a second run at it with one tap and offline capture in the mix.

For more details: read our take on the Android One Tap Mobile Notetaker.

Knowledge Base Agent, and the Meter That Starts September 16

Breeze Knowledge Base Agent

Knowledge Base Agent reads and extracts topics from your tickets, compares them against your existing knowledge articles, and surfaces suggestions for new articles plus edits to existing ones where the content is unclear, outdated, incomplete or off brand. You review, accept or reject each suggestion from the Suggestions tab. Professional and Enterprise. The change worth circling is the date: on September 16 the agent starts consuming credits, at roughly two dollars or two hundred credits a pop.

Put that number next to the other one on the page. AEO surfaces a recommendation, and taking it to content agent for a blog post runs a thousand credits. Knowledge Base Agent has been free for about a year, is free for another month, and after that costs a fifth of what a blog post does. If you have tickets and emails, and most organizations have more of both than they think, that is the cheapest content on the shelf.

Which is where Madelyn's take carried the segment. The setup was the familiar one: all the subject matter expertise in an organization is already written down, sitting inside emails, written by people in service and operations who do not have time to make content and would not call what they are doing content anyway. They are writing novels in email to solve one customer's problem, and those are articles.

Madelyn took it from the marketer's side of the table. Go to a subject matter expert asking for marketing input and "they're often like a deer in headlights. They're like, I don't know what to tell you to do marketing wise. I don't know what content, like I'm not a marketer." Her answer to that has always been to stop asking them to think like a marketer. "You have so much like gold information in your head right now. Just like say anything." Tell me what you did yesterday. Tell me what you are dreading today, and why. "Don't filter yourself because I will do the filtering for you." The gold nuggets show up when you are sitting beside them, or you are a fly on the wall in their team's meeting. Her read on the agent was that it is that seat, made available when nobody from marketing is in the room.

The second half of her take is the one worth pinning up. A knowledge base is not only a source of content. It is a marketing asset in its own right. Being able to say that you keep one, that you keep it current, that you can point to the proof behind every claim you make instead of promoting something you cannot back, is itself the benefit. "The fact that you have a knowledge base itself is a marketing goldmine."

The org-chart problem came up alongside it. The knowledge base still lives under Service Hub, which is why it gets treated as a success and service tool, and it is one of the best black and white sales tools there is. No marketing language, no fluff, here is exactly how this works, easy to walk somebody through on a call and easy to send after. Marketers told to support sales reach for content agent and a blog post, which is a completely different tone, while the article that would actually answer the question sits a click away.

One practical gate turned up on screen. The agent requires at least five closed tickets to run. Casey had plenty of closed tickets in the portal but only two in the out-of-the-box support pipeline, which raises a question the segment left open: does it count closed tickets across every pipeline, or only the one? That is a product team question and it is on the list.

Why it matters: the credit math is the whole story here, and there is a month left on the free side of it. Two dollars for an article drawn out of work your team already did is a different proposition from a thousand credits for a blog post, and the table said as much: at two dollars a pop, more value than a lot of what that budget goes to now. The plan somebody floated out loud is the one a lot of people are about to have. "So basically I'm gonna go figure out how to create tickets on every email I've ever received real quick and then run knowledge agent until September."

For more details: read our take on Breeze Knowledge Base Agent.

Friday Horoscopes

The last slot on a Friday belongs to Madelyn, and this week she had material. "The ether like thrives on time being weird, so it really has been inspired this week." Twelve signs, twelve updates, and a weekend send-off.

Aries got lead stage and details surfacing in the Sales Extension sidebar, which means moving first and moving informed. Taurus got contracts created and edited directly in HubSpot with no quote required: "The thing you've always trusted, value you can hold and point to, no longer needs an invented middle step to exist." Gemini got Reddit conversations about your brand visible inside HubSpot, sentiment and all, which is finally hearing what gets said back. Cancer got the weekly customer health assessment landing in the customer success workspace: "You worry about everyone anyway, now the data worries with you."

Leo got the AI clips panel surfacing your best moments ready to post, because "you are always going to be seen. This week HubSpot just finds your best angle first." Virgo got the new other limits page putting every subscription usage number in one place: "You already suspected something was almost at capacity, but now you can prove it." Libra got deal routing with a balanced option and user availability, which is years of arguing for fairness in the routing logic arriving in the product. Scorpio got buying groups mapping every stakeholder with drag and drop clarity: "You already knew nothing closes alone."

Sagittarius got multi-account management on any Enterprise subscription, no longer Marketing Hub Enterprise only, so the barrier to managing more territory came down. Capricorn got meetings carrying a payment link end to end, configurable through the API, because you do not just want the close, you want it collected. Aquarius got the public API for pipeline object tags, defining and auto-applying tags outside the standard UI entirely: "You are never going to tag things the normal way." And Pisces got Breeze and global search merged into one entry point on mobile, so there is no deciding up front whether you are searching or asking. "The boundary you'd never believed in just stopped existing."

The open thread for next week is Chiron, your biggest challenge and your biggest opportunity in the same place. The ether did not have an answer for that one this morning, but the question it raises is a good one: which update is your biggest challenge and your biggest opportunity at the same time? 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 week.