Build It Where You Work: App Builder Learns to Count, Customer Agent Knows Who You Are and Why to Start With Breeze

Another Orange Morning Recap: Friday, October 30, 2026

The day before Halloween, Madelyn Donovan joined Chris Carolan and me for the Friday show, and we spent nearly all of it on two updates. Madelyn asked a question on each of them that helped the rest of us, and by the end we had run past the point where the horoscopes usually go.

Here is what we got into: Chris's report from the Houston HUG, Friday's events, a Customer Agent update that passes the visitor's verified email into API requests, and a long conversation about Build with Breeze App Builder, which can now total up CRM data at scale. That one turned into a talk about building where your team already works, what that does to the marketplace and why the first move is still to ask Breeze.

Before the Updates: Costumes, the Houston HUG and Friday's Events

Chris asked the Halloween question first. I do not have a costume; I have a Corgi onesie that I put on most Saturdays because it is easy, so the timing is a coincidence. Madelyn told us she surprised herself by not having one either, and Chris gave her permission to skip it.

Chris then walked us through the Houston HUG he restarted on Thursday, with Agent Hub, Context Home and how to build with Breeze on the agenda. Two people from the HubSpot team joined, and the session ran ninety minutes. He told us about a moment when Breeze asked which company record to test an agent against and could not find the one he typed. Chris's take on that moment: "the best thing you can learn with AI is how to say no." When Breeze asked him to go and get the record id, he answered "no, period, you," and Breeze went and found it. He also said that Breeze agent costs were cut significantly on Thursday, and that a run he saw during the session came in at about half the price of the same agent's earlier runs. It was hard to get people to share their screens and build, he said, so he started building an agent himself.

On the calendar: Hubsessed Office Hours is today with George B. Thomas, the HubSpot Super Admin edition, on the Office Hours page. Last week's session was about collaborating across all the places we now build with AI, and Sharoze joined us from the Collective. There is an AEO 101 HUG on Saturday, and my guess was that it is a different time zone, which Chris confirmed is a Saturday evening networking hour in India. Next week Zach has his monthly HubSpot updates HUG and I have my monthly Women of HubSpot HUG. Chris is also targeting December 10 for an in-person CPQ workshop in Houston.

Two Updates, Both Worth the Time

Customer Agent Actions Now Include the Visitor's Verified Email in API Requests

Only one update had landed that morning when we started, so we counted a couple from the day before that came in after the show. Chris read the title and what it is: Customer Agent now adds the visitor's verified email to outgoing API requests, for actions that have email protection turned on. I read the why. Actions that call your own APIs need a reliable way to identify the visitor, so the agent now sends the verified email with each eligible request, and you no longer have to ask visitors for it or build custom middleware to pass it along. Your systems can use that email as a lookup key and return the right data, such as order details.

Madelyn said what the rest of us were thinking, which is that it sounds like something that should already have happened. I admitted I was a little confused, and Chris took it. His read is that logged-in portals are the use case. Before, the customer had to give an email at some point in the conversation, and that is not the worst thing as a verification, but think of a store where you are already signed in: "We're logged into the system and knows who we are." If I have already identified myself, he said, I want the system to stop asking in most cases, short of two-factor authentication and those security measures.

I came at it from the marketing side. You can pre-fill form fields for known cookie contacts, and I have still kept a confirm email field in places because the address on file is sometimes wrong. So for me "there's pros and cons either way," and if I said keep me logged in and then got asked for my email, "It's potentially annoying." Chris agreed and added that agents will get better at reading context, including how the person talks to them, and will ask directly when something does not sound like the person on record. He also drew the line between the two cases: a cookie and a logged-in portal are different, and "one's more fragile than the other, I'd say." If a visitor never accepts cookies, the agent will keep needing the email.

Why it matters: this is a quiet piece of plumbing, and it is useful when your agent has to look something up for a person. Decide which of your actions should depend on the verified email and which should still ask, and do it knowing that how the visitor arrived, logged in or on cookies, changes how sturdy the answer is.

For more details: Customer Agent verified email in API requests.

Build with Breeze: App Builder

Chris asked which new one we had not seen the day before had caught my eye, and mine was Build with Breeze App Builder for customizing your HubSpot account. Madelyn wondered why we had not done it Thursday; it landed after the show. Chris had brought it up at the HUG while people were asking what all the Breeze names mean, and said that "All the different ways that you're starting to see the word Breeze makes it super confusing for folks." The phrase "customizing your HubSpot account" is technically correct, he said, but it has to be explained.

He read the explanation: a conversational no-code tool that lets you describe a custom app in plain language and have it deployed directly into your HubSpot portal. No developer needed. The app goes live as an app page in your HubSpot navigation and reads your real CRM data each time it loads, using your own user permissions. It is for the questions that reports, dashboards and views do not answer, a page that combines the exact objects, properties and layout your team works from, presented in a way that does not exist out of the box.

I read what is new. The app builder can now summarize CRM data across all your records, including counts, sums, averages and percentages, grouped by any property or by date. Before this update, apps that needed totals had to add up records one page at a time, which broke once a portal had more than two hundred matching records. Summary apps now return accurate numbers however much data is in the portal, and if you are a current beta user whose app showed wrong or partial totals, you can ask App Builder to rebuild those totals and redeploy.

Madelyn asked whether this was something you could already do through the MCP, just not with Breeze, and then answered herself: "It's the word app." Chris explained why totals mattered. When we first started plugging AI into CRM data from outside the CRM, with more than a thousand records, accurate counts were not happening, and counting a hundred thousand records without structure uses a lot of tokens. His read is that this update brings structure that lets the work stop being token-based every time.

Chris showed his screen to make the case. The developer platform came out at last year's INBOUND, and people who are not developers have been building on it ever since. His Value Accounting page is an app page that works on the same architecture as UI extensions, and a content calendar was one of his first builds. He builds some of these in Claude Code, where an app card or a custom quote template can be in HubSpot inside thirty minutes, and his point was that Breeze Builder now does it all in the developer platform: "you don't have to do the code. There's code though." He pulled up a time and activity tracker in draft mode and took a suggested value-first readiness scorecard for a spin. He used the value entries behind Value Accounting to show the other half. The old way was to ask an agent to move a value entry to a confirmed stage, which costs tokens every time. Now there is a button: "This is a non-AI token-based way."

Madelyn gave us the translation, and it was a good one. Before, "I think what we're saying is we could do UI extensions or we could do app pages through the MCP, with [Claude] or with GPT or whatever." The difference now, in her words: "now we can create the apps in HubSpot, but then also use the app in HubSpot. And we can actually use it like you would anything else in HubSpot." The user can click through it directly instead of only asking an AI questions, and building and using it in HubSpot is lighter on tokens.

Chris tied it to the Collective. One of our members had been using the Collective management app outside HubSpot, and they brought it into HubSpot last weekend. He is still bullish on the value of HubSpot in this moment, because "most folks do not want to go into the command line." Right now it is free to build an app if you have access to Breeze Builder and the right permissions. He also pointed out that you have to be able to get yourself into a conversation with Breeze to get here, and that "go fix everything for me" is not a request an admin can act on, because they do not know what is in your head. He and Nico are running a three-week boot camp on December 1, 8 and 15 on how to use Breeze effectively in HubSpot and HubSpot AI.

The suggested app Breeze offered Chris was relevant because, as he put it, "my data model is amazing." I added the other side: "you have a perfect, amazing data model" is great, but "most people don't." I told the group about a client call from Thursday. They have a weekly sales meeting and want reps to update or review certain data points beforehand, and we were working out whether that is a view, a dashboard or something else; the proposed answer was a dashboard per rep. I had not thought about teaching them a Breeze skill or a Claude skill instead. Then "I read this this morning and I basically built it." It is not perfect yet, but a working version beats a plan.

Chris loved that, and it fed his next point. When the thing comes out of a conversation, the old motion goes away: "I'm going to put this through the mail slot and then you're going to go away and figure it out," then proof of concept number one arrives, you are busy for four weeks, and "now we don't even care about the problem anymore." His summary: "This is a different way of working," and if you have a conversation with Breeze, things start going better, even if what Breeze helps with first is how your system works.

Madelyn raised the marketplace. At last year's INBOUND, with Agent Hub, HubSpot talked about making your own apps and listing them on a marketplace where others can opt in. "Do we think that this also is related to that now being a lot more possible?" Chris said there is a path there, and that part of the reason for the update is "what do you need a marketplace if you can just build this." You may still pay for plug-and-play where security and compliance are involved, but every app tends to have a limitation that takes you into custom work anyway. His line: "a very underrated part of AI is that you can build this and be, okay, yeah, that's the thing that I want." He described asking Breeze whether anything on the marketplace does what you need, and having it tell you which of the properties an app adds make sense for you and which do not. And discovery changes with that: "for years we've had three month discovery, scoping things, because that was the only way we could communicate with each other," and now you can start that communication right away.

The last stretch was Chris sharing questions from the HUG. Start with "have you asked Breeze yet?", he said, with the exact thing you typed into the form, so you do not wait for a workshop to find out. Another of his favorites was asking what the agent and the person receiving its work each need to succeed, which keeps you from steering Breeze with the objects you assume you should use. He is "not a developer" and has "never built HubSpot apps in my life," yet the expertise he brings in data models and process ownership is what makes any idea someone brings him something they can do. The scariest example was a request to give an agent the job of adding options to CRM properties, which prompted the question of whether that should be an agent at all, since a dropdown with a hundred and fifty options usually points to a data model or process problem. Breeze, he expects, will start coaching that way. I added that I showed the Will It Breeze wheel to a client on Thursday, and it asked about payments they do not record in HubSpot, so Breeze came back saying "this isn't the right question."

Why it matters: accurate totals are what turn an app from a demo into something a team opens every Monday. If you have a recurring meeting where people review the same numbers, tell Breeze what you want that page to show and see what it builds. The part that holds the whole thing up is your data model, and the people who benefit most are the ones who can say clearly what they need.

For more details: Build with Breeze: App Builder.

The Sign-Off

Will It Breeze did not run this morning, and the horoscopes did not either. Chris said we got to the updates "at the expense of horoscopes, unfortunately," so they are bumped to next week. Madelyn has her crystals right there at her desk, and mine are on standby too. You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you next week.