Tuesday, October 20, 2026, with Casey Hawkins, Chris Carolan, and Ryan Ginsberg

Another Orange Morning Recap: Tuesday, October 20, 2026

Tuesday is Ryan Ginsberg's day, and he was in the top right tile the whole morning next to Chris Carolan, with Casey Hawkins on her last full working day before a week away. Chris opened with the new events calendar on anotherorangemorning.com, had Casey click through it cold, and then the three of them worked a short list of updates that kept landing on the same question: who, exactly, is the human checking this?

Here is what we got into: the HubSpot community events calendar, Flexible Defaults for Account Cleanup, the dunning link you can now send before a payment fails, bulk actions on Sensitive Data scan results and the redacted email bodies update it pulled back in, and a social post workflow that Casey built by hand while Chris had Breeze build the same one, which became the day's Will It Breeze.

A Calendar for the Whole HubSpot Community

Chris put a link in the chat and asked Casey, who had not seen it, whether it was intuitive. The new events page at anotherorangemorning.com/events pulls HubSpot-led and community-led events into one place: HubSpot User Groups, office hours, webinars and other gatherings, color coded, shown in Central time. Casey's first question was where the data comes from. It lives in our HubSpot on the Listings object, and most of it is pulled from events.hubspot.com.

Two things on it worth your attention this week. The Admin HUG later today is the HubSpot connector for Claude, and the AirOps HUG is Nate's talk from UNBOUND, which Chris recommended and may stop by after the show. The one he is most excited about is the Houston HUG on October 29, remote with the Agent Hub team, building an agent over ninety minutes starting from Context Home. The same calendar shows up on Hubsessed, The Road to UNBOUND and Value First Studios, because it is all one record in the portal. Chris was pleased it put Madelyn Donovan's picture next to the HUG she is leading.

Flexible Defaults for Account Cleanup

Account Cleanup's custom policy can now drop many of its default guardrails. Cleanup can delete in-use or published assets based on your own filters, and the lookback window can use create date, publish date or last activity date instead of only last modified. HubSpot's reasoning is that the recovery options added over the last few months, including a full revert of a cleanup job, make it safe to give admins more control. It is Enterprise only, and it moved to public beta on October 20.

Casey has used the tool, mostly as a way to audit, and has never turned on automatic deletion. The reason is the one this update partly solves: it only looked at date fields, and a lot of her assets are templates. An email or a landing page that sits in draft so it can be cloned looks exactly like something stale, and making sure cleanup does not delete those has been the blocker. Ryan asked the next question, which is whether deletion should be considering engagement data, not just dates. The answer in the room was that this is less about which live landing pages are quiet and more about the assets nobody has touched in a long time, like the page for the webinar that got canceled and never came back.

Why it matters: Chris's framing was the right one for the Enterprise audience this is built for. A lot of us loved HubSpot for cloning, so we became unintentional digital hoarders, and now there is a mountain of digital mess somebody would love to archive in one go. You can, with a tool like this, and you should take care as you do it. His bigger point is that zombie assets are not free: they take up space, bandwidth and attention, and messy context gets in the way of the AI that is now scanning your system. For more details: Flexible Defaults for Account Cleanup.

The Dunning Link, Before the Payment Fails

You can now copy a buyer-facing update payment method link for any subscription that was not generated from a contract, whatever the payment status. Until now the link only appeared after a payment failed. HubSpot's case is that failed payments are one of the most common causes of involuntary churn and most of them are avoidable: send the link when a buyer mentions a card is expiring, resolve the request in one step without collecting card details yourself, and skip the retry and recovery work. It is live for all hubs and tiers.

Chris admitted the only reason he knows what dunning means is Hubsessed. When the team took it over, he set his agents to monitor Beehiiv and Stripe all day, and they kept catching failed payments and reporting that the dunning link was still out. He did not know it was a special kind of link, only that you had to let the process retry three times before anyone could address it. This update is the proactive version, which is the right intent.

Why it matters: It also says something about how many permissioning gates sit around a simple thing. Should it be that hard to grab an update payment method link whenever you want to let a customer know? Chris read it as HubSpot taking another step toward a full-fledged e-commerce and online commerce management system, and thanked the Revenue Hub team for it. For more details: Update Payment Method (Dunning) Links Available for Subscriptions.

Bulk Actions on Scan Results, and the Redacted Email Question

The title stumped the room until the panel opened. Admins can now select multiple Sensitive Data scan results and redact them, or mark them not sensitive, in one step. One-at-a-time actions made large scan outputs impractical, so findings went unactioned; bulk actions make remediation feasible at scale. Enterprise only, admin only, public beta.

Ryan has never seen it in a client portal, and his questions were the ones that matter: how far does the scan go, properties or notes or emails, and what is actually happening under the hood once you mark something as redacted? What does it do to users of the system, and how is it maintained? Chris's addition was about the missing human: where is AI in this? Is AI the one telling you these five are not sensitive, and which person is going through the scan to confirm it is working? That is what the room found missing from the definition.

That pulled last Wednesday's update back in. Redacted email bodies is a portal-wide setting that logs that an email was sent without storing the body, for every user, no per-user or per-email option, which Casey read off the panel on her screen. Ryan asked why anyone would do this; he could not think of a use case. Casey could: there are companies that will not connect the HubSpot inbox at all because of what is in the bodies, a law firm being the obvious one, and for them it is a trade-off that is incrementally better than seeing no activity. She is not recommending it to anyone; she just thinks the use cases exist.

Why it matters: Chris's test is the question being answered. A redacted email tells you they got something yesterday, and nothing about what it said, so the visibility you wanted is still uncertain. If the only reason to turn it on is to keep opens and clicks measured, his advice was two words: don't do that. He also connected it to Monday's AI-Native Office Hours conversation about old contracts that say a client's data cannot be processed this way, while AI is everywhere. The honest move is to show up and ask for the five-year-old contract to be amended, because there is no way you are compliant just because the emails only exist in Outlook and not in HubSpot. For more details: Bulk Actions on Scanning Results and Redacted email bodies.

Will It Breeze: Build the Social Post Workflow

Trigger Workflows When a Social Post is Published now ships with two pre-built templates, a Slack notification and an email, plus guidance on the social post properties to use in custom workflows: broadcast status, channel type, channel and post URL. It is the first time social publishing connects to the rest of HubSpot automation. Marketing Hub Professional and Enterprise, public beta, with release expected November 3.

Casey's first reaction, when we first read it, was why do I need a workflow for this, and a Slack alert every time we post will not get annoying at all. Ryan's suggestion was to send it to his dad. Chris's answer is that the value is doing it inside HubSpot, with control and visibility over who engages, which is a big part of what a team asks for when it says build us a social strategy and then leaves a happy face in the share instead of on the post. Then he turned it into the day's Will It Breeze. No wheel this time. He pasted the update into Breeze Assistant in our portal and asked it to build the workflow for us. Breeze found the Slack notification action and a way to trigger when a post's broadcast status changes to success, asked where notifications should go, and published it. Meanwhile Casey built the same workflow from the template on her side, and the two landed in the same place. So, will it breeze? Yes, it will.

Casey's build raised the practical question: does it have to fire for every social post? It does not. She wants a Slack ping to the internal team when this show goes live, and the filtering gets you there; Chris's read is that most teams would align it with the campaigns their posts belong to. She also asked what other properties a social post carries, and Chris, who had just asked Nectar the same thing, flagged custom properties for social posts as something to keep an eye on.

Why it matters: Chris's lesson was the lesson of the morning. You do not have to talk to him, but at least talk to Breeze: use ten percent of the energy you spend on email on social and you will see results, and when a channel stops working for you, HubSpot has made it unbelievably easy to pick another one and ask Breeze to help you figure it out. Social is going to be a central part of AEO, and email, he is pretty sure, is not. Ryan added that the notification is one step and there are second and third steps behind it, Breeze actions and agents that suggest replies. Chris's close: a social post, a task, a meeting, these newer triggers that are not object-based are a big part of the switch to the canvas, so just have a strategy, and if you share it with Breeze it will help you execute it. For more details: Trigger Workflows When a Social Post is Published.

The Rest of Tuesday's Updates

Also on the board from October 19 and 20 and not pulled forward: the NetSuite Connector for Breeze Assistant is now live, custom coded modules can use quote totals and tiered line items and control PDF regeneration, the consolidated Channels page with send-from permissions is live, and Updated Report Visualizations is on the list. Breeze in Quote Templates and the two Breeze Assistant in Slack updates were Monday's conversation. Everything else that shipped is in the HubSpot updates feed.

The Sign-Off

Chris and Casey host Hubsessed Office Hours on Loop Marketing and AEO a couple of hours after the show, right after the Admin HUG. 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.