Show recap — Tuesday, August 4, 2026

Another Orange Morning Recap: August 4, 2026

Casey brought six updates. Ryan brought five. Almost all of them were APIs, which is starting to look less like a coincidence and more like a season. Ryan named it out loud partway through the show: help desk owned this program for two or three months straight, and now every morning there is another API release waiting.

Here is what we got into: the Contracts API and the structural gap it finally closes, the Teams API and the org-chart infrastructure most portals have never looked at, a meeting scheduler update that is not the meeting scheduler you think it is, the end of duplicate call records on recorded meetings, admin-configurable navigation, and a reusable metrics row that raises a harder question than the feature itself answers.

We Are In The API Era Now

The pattern was impossible to miss once it was said. Contracts API, Teams API, Sales Templates API, all in the same stretch. Ryan admitted he did not care about API updates six months ago and Casey said the same. When the show started, the API section was the part you read out loud in a funny voice for the developers. That has changed, and quickly.

Chris read it as a positioning signal rather than a coincidence. Revenue Hub and the agentic customer platform are going to be the message at Unbound, and a run of API releases is what it looks like when a platform is opening up the surfaces those two things need.

The Updates We Pulled Forward

Contracts API

A contract in HubSpot tracks the lifecycle of a relationship between a merchant and their buyer over time, holding terms of service, pricing, and duration for a set of purchased line items. The new API makes all of that reachable programmatically, so external systems can integrate with HubSpot's connected CPQ and billing tools and reach the business logic behind them without going through the UI.

The motion this opens up is the part worth sitting with. At an upgrade moment, you pull the customer's current contract into a quote, show them exactly what they have today, let them add or remove what they are paying for, layer in recommendations for anything else available to them, and write the whole change back into the contract when they sign or pay. Everything that customer has bought over time then lives on one record that anyone can open.

Compare that to what admins do now: close the deal won, spin up a new deal in a renewal pipeline, and open a ticket in a support pipeline to track the relationship going forward. Nobody designed that. It is what you build when the platform has no object for the agreement itself.

Why it matters: This closes the biggest gap HubSpot admins have been working around for years, and it is the release on this list most worth planning around. One caution before you get excited. It is built for recurring revenue moments and change management over time, so if you are expecting it to behave like general contract management software, check that assumption first. Also, adopting contracts means HubSpot now refers to you as a merchant. Plenty of businesses will benefit from this and approximately none of them describe themselves that way. Read it as company and move on.

For more details: our full take on the Contracts API.

Teams Public API

The Teams public API lets you create, rename, delete, and organize teams and manage membership programmatically. Until now the API could only list teams, and every other action meant clicking through the UI one team at a time.

Ryan's use case landed the value immediately. You have a spreadsheet of users and everything they are responsible for. Hand that to an AI session with the full context, let it reason about how the structure should work, then call the API and build it. That is real work removed, and it holds up six months later when the structure changes again.

The segment turned into a tour of the user object, which is worth your time if you have not looked at it lately. You can manage associations on users now, and under any user's setup there is a management hierarchy where you assign a manager and reports, which means your org chart can live in HubSpot instead of a slide deck. Chris was honest about the ceiling on this: it only starts to make sense once you actually have multiple teams and user types. Below that, note that it exists and keep moving.

Why it matters: Permissions are the obvious next step, and once you can build teams, build permission sets, assign permissions, and manage membership all through the API, team architecture becomes something you design rather than something you maintain by hand. People have been building HR-adjacent functionality in HubSpot for a long time, and the user management area is catching up to them fast.

For more details: our full take on the Teams Public API.

Customize Meeting Scheduler In The CRM

Read this title slowly, because it is not what most people will assume on first pass. This customizes the meeting create form inside the CRM, the one that opens when you click the meeting button on a record. You choose which properties appear and which are required in order to book. It is not the public meetings scheduler page.

The naming actively works against you here. Hover over the sales navigation on the left and it says meeting scheduler. The update is titled meeting scheduler. One letter apart, two completely different features. Casey reads every update on this show and still went in expecting something else, which tells you the phrase doing the real work, in the CRM, is easy to skim past.

Why it matters: Custom meeting properties have been available for a couple of months and have been useful, but the meeting interface itself stayed static, so those properties were hard to actually populate. This is the step that starts making them visible where people work, instead of requiring someone to go back into the meeting index page and set them after the fact. Worth tempering expectations on reach, though. Not many teams book meetings from this form in the first place, so it matters most if you are pushing everything onto the contact record and keep hitting buttons that do not do what you need.

For more details: our full take on customizing the meeting scheduler in the CRM.

Recorded Meetings No Longer Create Duplicate Call Records

As of Friday, July 31, meetings recorded with Notetaker or the Zoom, Microsoft Teams, and Google Meet integrations create both a call record and a meeting record. Opt into the public beta and you get only the meeting record. The change reaches everyone on August 31, and call records continue to exist for actual phone calls.

This one has been a long time coming. Having both objects generated from a single recorded conversation meant every portal quietly carried duplicate data, and anything built on top of it was slightly wrong in a way nobody was watching.

Why it matters: This will break reports. Not might, will. If call properties feed any of your workflows, or you report on calls, or your team reaches recordings through the call index page, plan the migration to the meeting object equivalents before August 31 rather than after. Two details worth holding onto: during the beta, adding meetings to a playlist, deal insights derived from meetings, and asking Breeze about meeting transcripts are all unavailable until the full rollout, so opting in early has a real cost. And there is an edge HubSpot cannot language its way out of, which is that a recorded phone call from a scheduled calendar item is not what recorded meeting is pointing at, and most people are not making that distinction in their heads.

For more details: our full take on recorded meetings and duplicate call records.

Admin Navigation Customization

Admins will be able to configure and assign custom left-navigation menus to specific users and teams, so people see only the tools relevant to them. This one is still in development, so treat it as a forward-looking statement rather than something to build a quarter around.

Ryan caught the loop right away, and it is a good illustration of how platform development actually moves. HubSpot ships an API so you can create forty teams programmatically, then ships navigation you assign per team. Which means the next thing you will want is an API to manage navigation for the forty teams you just made, because nobody is clicking through those by hand.

Why it matters: The feature people are really waiting for is arbitrary URLs as navigation links, which has been signaled as on the way. Enough people wanted this that there are apps built specifically to do it on top of HubSpot, and that is usually a reliable predictor of what gets absorbed into the platform. In the meantime, one practical habit for anyone who supports, consults, or coaches on HubSpot: add navigation to your initial audit list. What the nav looks like tells you a great deal about how a team actually uses the platform, and it takes five seconds to read.

For more details: our full take on admin navigation customization.

Reusable Metrics On Dashboards

You can now add a row of up to six metrics to the top of any dashboard, chosen from a default library or built with your own aggregations and custom formulas. Metrics support all object types including custom objects, they inherit whatever filters are applied at the dashboard level, and clicking one drills into over-time, by-owner, and by-team breakdowns. Only super admins and dashboard owners can add or modify them.

Casey pushed back on this at first, and the pushback was fair: a KPI report already gets you most of this. The distinction is that you skip the report entirely. Pick your object, pick your aggregation, done, with no report to build and then maintain. The filter behavior is the quietly useful part, because filters between reports and the dashboard itself are one of the most confusing things about dashboards, and metrics inherit the dashboard-level filters cleanly.

Why it matters: Here is the harder question the feature raises. Everyone wants the dashboard. Far fewer people can tell you what the number on it actually means. Before you add six metrics to the top of every dashboard in your portal, go ask five people in your company what one of those metrics means and see whether their answers match. If they do not, it does not matter how many metrics you clone. The same holds one layer down: a deal has been in a stage for forty-five days, fine, but is that good, what is the target, and what changes tomorrow because you now know? Getting the metric on screen is step one, not the answer.

For more details: our full take on reusable metrics on dashboards.

The Trust Conversation

The Teams API segment took a turn worth pulling out on its own. Casey brought a text from a previous client who had connected the API to Claude and, for the first time, edited something in HubSpot with it. His forms were creating marketing contacts and he needed that turned off across all of them. Doing it by hand meant opening every form and unchecking the same box. It took fifteen minutes with Claude and it was done.

Her question was the practical one: what do you tell the clients who still will not connect their portal to an outside model? Chris's answer was that it is trust in AI, not trust in HubSpot, and that the security conversation is a trap. There are too many variables in play and none of them are what actually drives the decision. His starting move is a conversation with Breeze's assistant about whatever problem is in front of them right now, inside their own portal with their own data. If that is not comfortable, connecting an external model never will be.

He also flipped the risk framing in a way worth repeating. If you are willing to trust fifty humans in your CRM without properly onboarding them or giving them context to the data model, they are already in there making decisions. An AI that knows the data model, knows the properties, and has the context can reason better than most of them. Ryan added the guardrails: read-only permissions scoped to specific parts of the CRM, and a human reviewing the build, because he has watched AI get ninety percent of the way there without building the right solution fully. Chris named the actual exposure as the messy middle, which is handing fifty people powerful tools with a note that says go get help doing your job and no enablement behind it.

Sign-Off

Chris closed with a teaser. Lookup fields are unlocked in the Value-First Team portal, and if Unboxing does not get there first, they will dig into lookup fields for associations next week. Judging by how often that question comes up, it will draw a crowd.

You probably already own the value you are looking for in HubSpot. You just need to wake up to it.