Show recap — Tuesday, July 14, 2026

Another Orange Morning Recap: July 14, 2026

Chris is out this week, so Tuesday's show had a friend in the co-host seat. Ryan Ginsberg joined me, and since Ryan spends most of his days inside UI extensions and integrations, he brought a builder's-eye view to a batch of updates that reward exactly that perspective. It is a small week for releases, but a few of these quietly retire workarounds that HubSpot builders have carried for years.

Here is what we got into: why Chris is running a bootcamp instead of sitting next to me, what file components mean for anyone building app cards, the legacy scoring sunset and its deadline, the automation updates that stop making you chain workflows together, and the social agent that finally learns from your own data.

Chris Is at Bootcamp, So We Had a Friend In

Chris is out Tuesday through Thursday running a HubSpot Academy mini bootcamp with Nico, the AI-Augmented HubSpot Stack mini series. It is three ninety-minute sessions across July 14, 15, and 16, walking people through where agents fit into their HubSpot stack and activating them on AI capabilities. HubSpot Academy is testing out these shorter formats, and I am really curious to hear how it lands, both from Chris and from a couple of friends who are in the bootcamp themselves. One of them told me she had to join because, unlike me, she does not get to talk to Chris every day. Pros and cons.

Which is how we ended up with Ryan in the chair. My warning to him at the top still stands: I am not great at staying on task when Chris is not here.

A Builder's-Eye View on Files in UI Extensions

Ryan picked the FileUpload and FileViewer components for UI extensions first, and it made sense, because he lives in this part of the platform. His take was that UI extensions were the best thing to happen to how he builds in HubSpot, and file handling was one of the last real gaps. Until now, if you wanted a proper upload experience inside an app card, you built the long way around: an HTML page loaded in an iframe, plus a backend to manage the uploads and write files back to the record. On one project, Ryan had to hand-build even the small touches, like letting users rename files or reorder how they appear.

Why it matters: The value of UI extensions is that they curate the record experience and protect users from messy data entry and stage progression. File handling belongs in that same category. You need one specific file, named correctly, in one place. Ryan's read was that these components turn all of that custom scaffolding into something you drop into the card and it just works. Anything that makes the powerful parts of HubSpot usable for the rest of us is a real win.

For more details: the FileUpload and FileViewer UI extension components public beta.

The Scoring Queen and the Legacy Sunset

I have a brand to uphold, so of course I took the legacy scoring sunset. This is the update with a clock on it. Legacy scores stopped updating back on October 3, 2025, so nobody has been actively scoring with these properties for close to a year. What is new is that the values and rules are about to be removed from portals entirely and will no longer be visible. Ryan made a sharp point about the product management arc here: HubSpot built the capability, shipped it to everyone, decided to replace it with something better, and is now walking a year-long migration all the way to removal. That is a lot of discipline to watch play out in public.

Why it matters: For most teams there is nothing to do. If you moved to the new Lead Scoring and Health Scoring tools, or you stopped scoring altogether, you are fine. But if you care about what your legacy scores used to say, this is the last window to keep it. I would not rebuild the old logic in the new tool, the new one is far more sophisticated and rebuilding rarely makes sense. I would just preserve the record. Take a couple of screenshots, hand them to your AI tool of choice, and ask it to write up what you used to score on. Ten minutes, and the history is yours.

For more details: the legacy scoring property sunset update.

Automation Is Done Making You Chain Workflows

Two updates landed on the same nerve, so we talked about them together. The first is being able to use a record you created in a workflow later in that same workflow. Ryan and I have both spent years working around this. You would create a contact in one workflow, set a flag on it, and use that flag to enroll it in a second workflow that did the actual work. For anything cross-object, Ryan's answer was usually to drop into custom coded actions and create and associate records by hand. He described a build where he needed a custom location record, a custom address record, and associations back to the company, all of it coded. His read now is that the whole thing can be rewritten natively. As someone who reads the updates every day, I have created so many properties that exist only to bridge two workflows together. This is the update that makes them unnecessary.

The bigger version of that idea is the agentic automation builder, which is in private beta and, per the announcement, will eventually replace the current workflow builder. That line stressed me out a little, and I said so. My brain pictures a workflow as a tree you read top to bottom. This new canvas can branch in more directions and does not have to anchor to a single object, which is more power and a real adjustment at once. The part that got both of us was the connector angle. The builder can work as a pure bridge between tools with no CRM update required, triggering from a Google Sheets row and sending a Slack notification. For years the HubSpot posture felt like get everyone and everything into HubSpot and you will be fine. But that is not how a lot of businesses run. Think about the accountants and bookkeepers you work with. This feels like an acknowledgment that we sometimes have to meet people where they already are, and AI is only making that more obvious. Ryan works with sales teams doing most of their work in Claude through the MCP connector and touching the HubSpot interface less and less. Headless CRM is coming.

One thread I want to keep pulling: the sales reps' oldest question about scoring is why did this lead score, and that is never obvious in the activity view. If an agentic flow can research the score itself and write up what actually drove it, that is a real answer to a real problem. The team behind this builder has been on the show before, and they are coming back around the end of the month, so we will get to ask.

For more details: using records created in a workflow later in the same workflow and the agentic automation builder private beta.

The Social Agent Grows Up

We closed on the tester program for the social content agent, the successor to the Social Post Agent from Unbound. The original generated posts from holidays and calendar events, and the most common feedback was simple: people did not want posts about random holidays. Ryan tested the original and, to be fair, it was impressively good at finding the most obscure holiday it could connect to you. It found Women in STEM Day for him. I told him that if I suddenly started posting every day about the random holiday of the day, someone should Slack me to make sure I had not been hacked.

Why it matters: The new agent researches your industry, reviews your past post performance, and checks what your contacts are asking about in the CRM before it writes a word, all in your brand voice. That maps to how I actually create social content. Most of my posts come from real conversations. At least once a week I hand Claude a transcript and ask it to write a post about one part of it. Seeing HubSpot lean into that same source, your own data instead of generic prompts, is the right move. It is a private beta for Marketing Hub Professional and Enterprise, and there is a hoop: you have to book time with the product team and commit to live feedback before you get in. I appreciate that, actually. There is always a learning curve with a new AI tool, and having the team walk you through it is a win for both sides. Ryan and I may or may not have talked about signing Chris up on the spot.

For more details: the social content agent tester program.

The Rest of Tuesday's Updates

We covered all five of Tuesday's updates on the show, and the full breakdowns, in reader-impact order with the tiers and beta status spelled out, are on the updates blog: HubSpot Updates: July 14, 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.