Show recap — Wednesday, May 6, 2026

Another Orange Morning Recap: May 6, 2026

A light Wednesday on the release calendar (only three updates landed yesterday) turned out to be a gift, because the show could run through every one of them and still get to a full Will It Workflow and a long-overdue Object of the Day. Email quality checks earned the most enthusiasm of the morning, with Casey at one point declaring it a big day for her personally as a self-identified email marketer.

Here is what we got into: subscriptions event data in the report tool, tags in dashboards, AI-powered email quality checks, a Will It Workflow that talked itself out of the workflow it started with, and a deep dive on the subscriptions object that Casey has thoughts about.

Three Updates, All Pulled Forward

Subscriptions Event Data in the Report Tool

You can now use subscriptions event data, including individual subscription statuses, in the report tool to build views and track subscriber data over time. The events include source of opt change, status change, date, and more. The product update page lists this as private beta, but it appears live in the tool for Marketing Pro, Marketing Enterprise, Marketing+ Pro, and Marketing+ Enterprise. To be clear: this is communication subscriptions, not commerce subscriptions, a confusion that has been around as long as both objects have shared the word.

Why it matters: Subscription engagement data has been a real gap in HubSpot's reporting for marketers who need to optimize email strategy, measure list growth, or explain unsubscribe trends to stakeholders. Until now, that data lived where you could see it on a record but not where you could analyze it across the database. Bringing it into the report tool changes that. Casey's reaction said it cleanly: this was a gap, and now it is not.

For more details: Subscriptions event data in Report tool private beta

Tags in Dashboards

You can now add, remove, and filter tags on dashboards, including bulk actions and filter-based selections, to organize and locate dashboards faster. Tags have existed on reports for a while, and this is the natural expansion to dashboards. Available across all Professional and Enterprise subscriptions.

Why it matters: Casey's framing on tags is that they work like a more dynamic foldering structure inside reports, which never got real folders despite every admin asking for them. Tags do the same job and do it better, because a single report can carry multiple tags (sales and marketing, for example) instead of having to live in one folder or get duplicated into two. The worst-case alternative, two folders with two slightly drifting copies of the same report, is exactly what tags prevent. Worth noting that Casey would start a tagging structure with Breeze help, because tagging and metadata management is one of the things AI is much better at than humans, and getting the structure right early avoids ending up with fifty random tags in week one.

For more details: Tags in Dashboards live

Email Quality Checks

Email quality checks are a built-in AI review in HubSpot's email editor. They scan an email before send and look for common issues: spelling and grammar, spam triggers, broken links, missing token fallbacks, date formatting, a weak first-sentence hook, off-brand voice, and how AI inbox assistants will summarize the email to recipients. Teams can also add custom AI-powered checks for specific voice, tone, or content requirements, and adjust severity to match how strict they want to be. This is in private beta for Marketing Hub Starter, Professional, and Enterprise.

Pieces of this already existed. HubSpot has been flagging missing token fallbacks and broken links for a while. The new piece is the much wider scope, especially the custom AI checks for voice and tone. Casey called this the part she is most excited about, and it ties directly to a problem she runs into with every team she writes for: the first email she drafts is never quite right because she has not built the model of the team's voice yet, and the only way to fix that is rounds of feedback until the edits are minor. Custom voice checks compress that loop into the editor.

Why it matters: The single newest signal in this update is the check for how AI inbox assistants will summarize the email. That is a different kind of QA than anything email tooling has done before. The reader who matters most might not be the human recipient; it might be the AI that decides whether the human ever reads the email at all. Building that check into the editor before send is an acknowledgment that email quality now has two audiences, and most teams are only writing for one of them.

For more details: Email quality checks private beta

Will It Workflow: Meeting, Google Drive, Trigger Approval

The wheel landed on a meeting as the trigger object, Google Drive as the app, and trigger approval as the use case. The setup was promising on paper: a kickoff or onboarding meeting completes, a shared drive gets created for the new client, documents get uploaded, and an approval gets routed to a manager. Meetings becoming a workflow trigger is new and worth flagging on its own; it opens a lot of automation paths that did not exist before. The new Google Drive app is also live and brings actions like create folder, create shared drive, upload file, and link existing drive.

Where the build hit friction was the approval step. Google Drive does not have a native approval action, and the available drive actions did not quite match the use case Casey wanted to solve. Breeze's recommendation, when she asked, was to use Drive for the asset creation step and route the approval through HubSpot's own systems: tasks, tickets, deal pipeline approval stages, or quote approvals in Commerce Hub Enterprise. The conversation kept coming back to a real distinction: approvals where someone needs to click a button in a system are a fit for workflow automation, while approvals that are really just a conversation between two people are not.

The takeaway: the workflow can work, but the value is in routing the approval through HubSpot's approval-aware surfaces, not through Google Drive. The bigger pattern this conversation surfaced is that meetings as a trigger, the new Google Drive app, and the maturing approval systems (deal stage approvals, quote approvals) are all coming online at the same time, which means use cases that would have been clunky six months ago are getting cleaner.

Watch the episode for the full build, and spin your own wheel at anotherorangemorning.com/wheel.

Object of the Day: Subscriptions

The first update of the day decided the object: commerce subscriptions, not to be confused with communication subscriptions, a distinction that has tripped up enough people that Casey told a story about Profoundly's first job posting, where four out of four proposals assumed the wrong subscriptions object. One proposal asked the right question (which subscriptions do you mean?), and that one stood out.

To find subscriptions in the portal, you go to Commerce, then Subscriptions. The CRM dropdown does not list it directly, which is a small but recurring source of confusion. Subscriptions has its own object record with custom properties, an editable data model, and association options, though notably it cannot yet associate with projects, services, listings, courses, or appointments. That last point is worth flagging if you are building post-sale workflows that would naturally connect a subscription to a service or course delivery.

Casey's primary use case for subscriptions is recurring invoices, which is exactly what they are designed for. Her primary frustration is that subscriptions are hard to edit once live. Editing a description on a live subscription triggers a notification to the client, which is rarely what the user actually wants when they are fixing a typo. Chris's read on why is fair: subscriptions are the fast-and-loose answer to the ARR/MRR problem, and the auditability layer that comes with the new contracts object is part of HubSpot's solution for the cases where edits need a paper trail. Both objects exist for a reason. The challenge is knowing which one fits which job, and HubSpot has not made that distinction as obvious as it could be.

The bigger thing this segment signals is that the commerce object family (subscriptions, contracts, and the rest) is still maturing, and the gaps between objects are where most of the real friction lives. Knowing where the gaps are is the difference between making the data model work for you and fighting it.

For more details: Subscriptions event data in Report tool private beta

The Rest of May 5's Updates

Full breakdowns of all three updates from May 5 are on the updates blog: HubSpot Updates: May 5, 2026

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.