Updates blog — Tuesday, July 14, 2026

HubSpot Updates: July 14, 2026

Five updates to walk through this week. We are still coming off the week of rest and about two months out from Unbound, which is the stretch where releases either slow down or speed up depending on what HubSpot is holding for the big stage. This batch leans small but useful, and a couple of them quietly retire workarounds that HubSpot builders have been living with for years.

One of them also carries a deadline. Your legacy scoring properties are about to disappear from your portal for good, so that is where we will start.

If you watched the show today, you already heard Ryan Ginsberg and me talk through most of these. If you did not: watch the recap to hear our thoughts on these updates and more.

Platform Updates Detailed

Sunsetting Legacy Scoring Property

This is the one with a clock on it. Legacy scoring properties stopped updating with new data back on October 3, 2025, so the scores have been frozen for close to a year. The next step is now scheduled: the existing legacy score values and their scoring rules will be removed from customer portals and will no longer be visible. This affects any Professional or Enterprise customer who still has legacy score properties sitting in their portal. The path forward is the newer Lead Scoring and Health Scoring apps, which bring decay, resets, and scalable rules that the old properties never had.

Why it matters: If you already moved to the new scoring tools, or you stopped using scoring altogether, there is nothing to do here. But if you care at all about what your legacy scores used to say, this is your last window to capture it, because once the values are gone they are gone. The move is not to rebuild your old scoring in the new tool. The new tool is far more sophisticated, and there are very few cases where rebuilding the legacy logic makes sense. The move is to preserve the record. Take a couple of screenshots of what you had, and if you want it in a cleaner form, hand those screenshots to your AI tool of choice and ask it to write up what you used to score on. Ten minutes now, and you keep the history.

For more details: the legacy scoring property sunset update.

Use Records Created in a Workflow Later in the Workflow

This one solves a problem HubSpot builders have complained about for a long time. When you create a record inside a workflow, you can now reference that record and its properties in later actions within the same workflow. HubSpot's example is a good one: in a company workflow, you create a contact, then add that contact to a segment and pull its properties into a task or notification for your team, all in the same flow. It is in public beta for Smart CRM, Marketing Hub, Sales Hub, Service Hub, and Data Hub on Professional and Enterprise tiers.

Why it matters: Until now, the workaround was to chain workflows together. You would create the record in one workflow, set a checkbox or a flag on it, and use that flag to enroll the record in a second workflow that did the rest. It worked, but it spread one process across multiple flows and made everything harder to read and maintain. For the more complex cross-object cases, the answer was often to drop into custom coded actions entirely, creating and associating records by hand. This update pulls a lot of that back into a single native workflow. If you have ever created a property that existed only to bridge two workflows together, you know exactly how much cleanup this invites.

For more details: using records created in a workflow later in the same workflow.

Agentic Automation Builder

The agentic automation builder is a new canvas that brings workflows, AI agents, and data from across your business into one place. You can start an automation from more sources than before, including CRM data, scheduled times, webhooks, and third-party integrations, then add traditional workflow actions, run AI agents, and branch based on what happens. The recent round of additions is worth noting: a run-on-a-schedule trigger, a send-email action, a find-associated-record action, a simulation mode that lets you test agents without spending credits or taking real actions in your portal, and estimated token and credit costs surfaced per agent run. It is in private beta for Marketing Hub, Data Hub, Sales Hub, Service Hub, and Smart CRM on Professional and Enterprise tiers.

Why it matters: The line in the announcement that stands out is that this builder will eventually replace the current workflow builder. If your brain pictures a HubSpot workflow as a tree you read top to bottom, this is a different shape. The canvas can branch in more directions, and you do not have to anchor it to a single object. That is more power and a real adjustment at the same time. The piece worth watching is the connector angle: the builder can run as a pure bridge between tools with no CRM update required, triggering from a Google Sheets row and sending a Slack notification. That is an honest acknowledgment that not every business runs entirely inside HubSpot, and it meets teams where they actually work. There is no action required today, and HubSpot says it will share transition details well in advance.

For more details: the agentic automation builder private beta.

FileUpload and FileViewer for UI Extensions

Two new UI extension components let you add file upload and file display capabilities directly to your app cards. Files are stored in a per-app folder in HubSpot's file manager, and uploaded files can optionally be attached to CRM records. It is in public beta across all hubs and tiers.

Why it matters: Until now there was no native way to handle files inside UI extensions. If you needed a curated upload experience, you built a workaround: an HTML page loaded in an iframe, plus a backend to manage uploading the files and writing them back to the record. Anyone who has done that also had to hand-build the niceties, like renaming files or controlling their order. These components turn that whole detour into something you drop into the card. For builders who use UI extensions to protect users from messy data entry and keep them inside a curated record experience, file handling was a real gap, and this closes it.

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

Seeking Testers for Social Content Agent

HubSpot is looking for testers for the next generation of its social agent, the successor to the Social Post Agent that debuted at Unbound. The original generated posts from holidays and calendar events, which for most B2B marketers had little to do with their actual business. This one works differently. You tell it what you want to post about or ask it for ideas, and it researches your industry, reviews your past post performance, and checks what your contacts are asking about in the CRM before it writes anything. It works in your brand voice and saves drafts to HubSpot's social app, currently for LinkedIn with more networks coming. It is in private beta for Marketing Hub Professional and Enterprise customers, and there is a real hoop: you have to book time with the product team and commit to live feedback before you get access.

Why it matters: The most common piece of feedback on the original agent was that people did not want posts about random holidays. They wanted help turning their own content, blogs, case studies, emails, and industry news, into posts that actually sound like them. That is the whole shift here. Because the agent pulls from your HubSpot data, including past posts, brand voice, AEO recommendations, and CRM conversations, the output reflects your business instead of generic AI writing. The research happens before the writing, which is the right order. It is also a good reminder that these agents are only as good as the context you have in your CRM. The better your data, the better the drafts.

For more details: the social content agent tester program.

Key Takeaways and Next Steps

Automation is getting less siloed: Two of this week's updates chip away at the same old pain. Using records created in a workflow later in that same flow, and the agentic automation builder pulling agents and workflows onto one canvas, both point in the same direction. Fewer chained workflows, fewer bridge properties, less dropping into custom code just to do something cross-object. If you have workarounds standing in for a single flow, this is the season to start untangling them.

HubSpot AI is moving from generic to grounded: The social content agent and the agentic builder share a theme worth naming. Both lean on your actual CRM data, your past posts, your conversations, your associated records, rather than producing something generic. The value is real, but it shifts the work. The quality of what these agents produce now depends on how well your CRM is populated. Clean, complete data was always good hygiene. It is becoming the thing that makes AI in your portal actually useful.

One deadline worth ten minutes: The legacy scoring values disappear from portals this week. Most teams have already moved on, and that is fine. But if you want a record of what you used to score on, capture it now with a couple of screenshots before it is gone for good.