From the show
Chapters
- 02:05Good morning, HubSpot Nation: Monday, November sixteenthTopic
- 02:16How are we doing this morning?Question
- 02:34A proper frost, finally, and a garden still to put to bedTopic
- 03:20Where can we take this? A lot has happened since last weekQuestion
- 03:43The earthquake has happened, and now we await the tsunamiTopic
- 04:22The product Dharmesh is describing every day on LinkedInTopic
- 04:41Headless HubSpot, Customer Relationship Harness or AI Native CRM: do the words matter?Question
- 05:28What have you been hearing out there?Question
- 05:34Not a course correction: an evolution, and a doubling down on velocity and experimentationTopic
- 07:37Follow Dharmesh: awareness is the gapTopic
- 08:19Nobody can keep up with HubSpot or AI: keep up with your businessTopic
- 09:20A bombshell update: Repeat Actions Over a List (looping) in Agent HubTopic
- 10:38Why it matters: a full sequence, branches included, on every recordTopic
- 11:19Who gets it? Down to StarterQuestion
- 11:57Up to one hundred repeats, and credits for every record processedTopic
- 13:27How long has the community been wanting this?Question
- 14:21Were we ever using custom coded actions for this?Question
- 15:13Why talk to Breeze about loops inside HubSpotTopic
- 15:55Another experiment: looping across associationsTopic
- 17:31When the deal reaches quoting: an executed NDA from everyone on itTopic
- 19:50Strategy conversations with HubSpot context, outside HubSpot structureTopic
- 20:39The HubSpot connector for Claude: a new experience and pinned appTopic
- 22:07A LinkedIn thread: is the Claude connector all you need?Question
- 24:08Do SaaS tools compete with Claude as a super app, or integrate?Question
- 25:54Pulling action items from client meetings through ClaudeTopic
- 26:54Asked at the admin HUG: does the AI context layer come through the connector?Question
- 28:00Capabilities drift when everyone connects their own toolTopic
- 30:04Shared central context anchors what AI producesTopic
- 32:43The HubSpot home in Claude, as the connector describes itTopic
- 34:00Structured or unstructured: when to lean on Breeze, when on ClaudeTopic
- 34:33Anything else from last week's updates?Question
- 34:46Build on property settings with the Properties Schemas APITopic
- 35:42Why are you so excited about it?Question
- 37:13Roll-up and sync properties by API: thirty manual actions down to twoTopic
- 39:33The contract for who fills in a property, and whenTopic
- 41:09The link icon on each update: hand it to your AITopic
- 42:36A new segment: The Refounding Request ListTopic
- 42:59If we're refounding HubSpot, what do we want to see addressed?Question
- 44:09The first request: email automation, every kind of emailTopic
- 46:07Meeting reminders: twenty-four, forty-eight and one hour outTopic
- 46:44Stop treating email as a different kind of communicationTopic
- 47:25Something that starts to tackle this: the marketing studio of a campaign recordTopic
- 48:41Document the communication strategy: who, when, why, and who owns itTopic
- 50:18Email coherence: a fair first refounding requestTopic
- 51:27The portal's data is one witness, not how the business runsTopic
- 51:52How a business works, on one slideTopic
- 54:08Credits per email send, and what 'email' means in your portalTopic
- 56:19There are just emailsTopic
- 56:28That's where we'll wrap: Casey is out this weekTopic
Another Orange Morning Recap: Monday, November 16, 2026
I was out this morning, so this recap comes from the tape. Chris Carolan had the room with Joshua Oakes, our Monday Friend of the show, and the two of them covered a lot: the HubSpot refounding news, two updates that landed on each other, a third update that was Oakes's own pick, and a new segment Oakes started late in the show. Will It Breeze did not run.
Here is what they got into: where the refounding news leaves us, then three updates, Repeat Actions Over a List (looping), the HubSpot Connector for Claude and the Properties Schemas API. Then Oakes introduced The Refounding Request List and made the first request, which was email in one place.
Where the Refounding News Leaves Us
Chris opened with the date and asked how Oakes was doing. Oakes was doing all right, and he had a gardener's report. "It's like two weeks and two days too late, but we just got a proper frost here, which I keep tabs on as a gardener." Then Chris asked where to take the morning, since a lot of news had dropped after last Monday's show, and Oakes answered in one line. "The earthquake has happened on the other side of the ocean and now we await the tsunami, maybe."
Chris brought up the updates page for a little normalcy, and then gave his read on the news. HubSpot has been describing the same reality in a lot of different words, Headless HubSpot, Customer Relationship Harness, AI Native CRM, and he does not think the label is the point. "I'm not sure it matters which words we use." What matters to him is the habit. "For me, it's as simple as get comfy talking to your AI assistant of choice." If we embrace that, he said, the systems, context and data around us need to support it.
Oakes did not read it as a reversal. He said it does not look like a course correction, at least from what can be seen so far, and he put the shift this way. "I think it's maybe an evolution and a doubling down on velocity and experimentation that we're seeing here."
Chris came back to where the gap is. "Follow Dharmesh at this point. He's very transparent. I think awareness is the gap at this point." His advice for anyone helping other people through this is about attention. "Nobody can keep up with HubSpot or AI or whatever they're developing. You should be keeping up with your business and what it needs and what your users need." Then you hand that to Breeze, or whichever AI you choose. He added a note about the people we work with. "Just like they never wanted to get good at HubSpot, they don't want to get good at AI either."
Repeat Actions Over a List (Looping)
Chris raised the first update himself, because it was a good example of what he had just been saying. "Things like this are going to keep happening, where this is like a bombshell update." It is Repeat Actions Over a List (looping), in private beta in Agent Hub. Chris put it on his screen and read the What. It is a new action in the Agent Hub workflow builder that runs a set of actions once for each record in a list, or a set number of times, with the actions inside the repeat container running in order for each item. Oakes read the Why.
Why it matters: until now, acting on a list meant building workarounds, or pointing a single action at a list with no per-item logic. Repeat lets you run a full sequence, branches included, on every record. The example on the page is an agent reviewing each stale deal and the workflow then creating and assigning a task for it. Oakes had a note on that example, which is that you would probably just enroll a list of the deals and let the logic create the task.
Chris asked who gets it, and the answer was down to Starter. Oakes explained why. "These are going to be purely credit priced workflows, not hub or tier constrained workflows." The page says repeats go up to one hundred, and credits are used for every record processed, so total usage depends on the size of your list.
Chris liked the name more than he expected to. "Users are never … say, can you create a for loop right here?" His point was that people ask for what they want in plain words, so "repeat is probably the right word so that you can just say, oh, how do we repeat this with this list? And now AI is going to know where it can go to do that."
Chris asked how long the community has been wanting this, and Oakes had the honest answer for anyone who has built in HubSpot for years. "I have Stockholm syndrome or something … my pattern library in my head is entirely founded on a world without this." Chris laughed and made it concrete. "Your for loop namespace does not include the word HubSpot." Then he asked whether custom coded actions were ever used for this. Oakes said for sure, and that when this reaches public beta, or general availability, the workflow action filter is what he will look for to see where a portal can replace custom code. He is curious how the credit consumption compares. "It'll be interesting to balance credit consumption to see what credit consumption across custom code action versus these loops will look like."
Chris saw something bigger in the exchange. When you ask Claude or GPT about loop-like things, he said, it points you to more complex solutions, like building a custom-coded workflow action. This is "probably a great example of why we want you to start talking to Breeze inside of HubSpot."
Oakes had a second place he wants to try it, which is across associations: set a property on a company and make sure every contact with a given association label has matching values, or check everyone in the buying group when a deal reaches a stage. His worry was the describing. "I hope Breeze is really good at these because it's in an area where describing those requirements is hard for beginners and advanced users." His example was a quoting stage where everyone on the deal needs an executed NDA. Chris liked where it goes, since the agent could even read the context of the record, and the check could be as simple as checking the box. "And now you can pass go. Maybe you get to collect two hundred dollars." Oakes put that kind of build in his own terms. "That's an example of the here be dragons area of my HubSpot map."
The HubSpot Connector for Claude
Chris moved right into the next update and pointed to the connection. When you can do some of this outside of HubSpot, you can have the strategy conversation without forcing the way it has always been done into the decision. That is why he said you might want some conversations to run outside Breeze. "Not letting yourself get boxed into the way it's always been done in HubSpot or what's available to do in HubSpot."
The update is the HubSpot Connector for Claude. Chris read the What from his screen. It is a new full-screen experience you can pin to the sidebar in Claude, where you can see which contacts are waiting on a reply, review and create tasks, and manage follow-ups in one place, and ask Claude questions about your HubSpot data from chat. Oakes read the Why.
Why it matters: keeping track of customer follow-ups often means moving between your inbox, your CRM records and your task list. With the pinned experience you see contacts waiting on a reply and open tasks in one place, start a follow-up task, have Claude draft an email from your HubSpot context, and review it before sending. Chris added his own list of things the page does not include, sticky notes, notebooks and voicemails among them.
Chris had seen a LinkedIn thread arguing that headless, credits and licensing do not matter because the Claude connector is all you need, and he had commented on it. His answer was that those are exactly the things that make the connector work for you. "All the stuff that you just said that doesn't matter are the things that are going to make your [Claude] connector work for you, right?" He thinks all of this is meant to make the connector experience better, "so that you can spend your [Claude] tokens on other things than recreating like HubSpot surfaces and actions."
Oakes took the long view. He asked whether platforms like HubSpot compete with Claude, which he described as quickly becoming a super app, or integrate with it, and said he does not know the answer. His near-term read is that you can do things in Claude and other connected AI tools that you can't do directly in HubSpot, while Breeze is far more capable than it was a few months ago. And his hope is plain. "I would love HubSpot to be as good or better at that, particularly given like context."
The part of his answer I would underline is about clients. He asked at the admin HUG whether the AI context layers in HubSpot carry through when you use the connector, and he does not think the answer is in yet. Meanwhile he sees people at every level connecting their own tools. "I am seeing drift." He described two people attacking the same problem and landing on two different numbers for the gap in a sales process, one at twelve million dollars and one at forty-five. His line on that is one to keep. "If you think you found a forty-five million dollar problem, you need to put a lot of diligence into verifying that and making it visible, provable, et cetera, rather than just asserting it."
His fix is shared context kept in the platform. "The more that a platform like HubSpot has that shared central context, like, here's our sales methodology, here's our sales process, here's, when we say leads, here's what we mean, right, all the way back to the foundations." If people do not agree on that, he said, two people building lead reports with AI will produce very different numbers. And when the connector suggests a task, he wants it working from the documented sales process rather than inferring the next step because it seems like it should be the next step.
Chris agreed completely. "This is why headless HubSpot is a thing." He wanted to show what the connector looks like in his own Claude, the first time he had explored it, but that window was never shared on screen, so the show stayed with the update page. He read what the connector says about pinning it, noticed a meetings beta in there too, and summed up where HubSpot is going. "They're building the whole stack over there." He closed with a way to choose between the two. Where the structure is already in HubSpot, lean into Breeze to understand your data and relationships. "The less structure and the more spread out the context is, I think that's when you lean towards Claude."
The Properties Schemas API: Oakes's Pick
Chris asked whether there was anything else from the last week that Oakes had hoped to get to, since he always starts the week out. There was. Oakes had posted it himself, an update that dropped the same day as the refounding news. Chris put it up and said the twelfth, and Oakes set him straight. "It was on the tenth." Chris said it got his attention, and Oakes agreed.
The update is the Properties Schemas API. Chris read the What. It brings new properties functionality to the API, including rollup and sync properties, field level permissions, validation rules and richer property metadata. Then he asked Oakes why he was so excited, and nobody read the Why. Oakes explained why. "This is a scenario where the why does it matter isn't mostly a restating of the what is it."
He builds a lot through a pipeline connected to a portal by a dev project, with agents that read his design against the developer documentation first. He gave the reason. "Training data is often wrong on how HubSpot things work." Rollup and sync properties used to be the part someone had to do by hand, or have Claude in Chrome do by hand. For the patterns he builds regularly, the numbers moved. "There's like thirty manual actions because these were not available via API." Those builds went to two. Chris's reaction was short and fair. "That's a lot."
Oakes widened it from there. "I love seeing the footprint of the API coverage expand into all of these different areas." Anyone who inherits portals knows there are hundreds of settings buried in places you have to go in and twiddle, and this does not touch all of them, but it pushes in the right direction.
Chris came at it from the documentation side. He remembers when HubSpot first documented the field inside a property, and his agents asked whether they could fill it in through the API. Not yet then. What his agents started calling the contract, the what, who, when and why of any single property, has been missing inside HubSpot, and now you can give it to your agents. The result, in his words: "They will not break the contract when it's there."
Oakes finished with how he put the update to work. He copied the link from the little link icon on the update page and gave it to his HubSpot Ops Claude repo. He asked it to add the new properties, and to account for the fact that beta features get rolled back sometimes, so a failed run does not pass silently. Claude read the doc, worked for about ten minutes, committed to the repo and refreshed his Claude plugins. "With less active time than it took me to read the update, that deploy framework was ready to go."
The Refounding Request List
This one was new, and it was not an update. With three minutes left on the clock, Oakes introduced a segment he had not planned a name for. "I should have thought of a name for it. The Refounding Request List." Chris was in. "All right, let's do it." "Okay. I like it." The question that frames it came from Oakes. "If we're refounding HubSpot, what do we want to see addressed?"
Oakes made the first request, and he made Chris guess the area first. He described something that "causes no end to confusion, frustration, and configuration headaches" and asked what part of HubSpot he was talking about. Chris guessed filters, and Oakes steered him. "It's more client facing, which is email automation."
His request, filed as a refounding request ticket, is about the number of places email lives. Transactional email, sequences, marketing email, one-to-one email and templates, plus about a half dozen emails that can only be configured and sent from buried spots in other parts of the UI. He gave meeting reminders as the example, emails you cannot style to match the others, and added that SMS has the same problem. His ask was simple. "That's all got to come into one place. Like we need to stop treating email like it's a different kind of communication than every other one."
Chris took it from there. "All right, let's go there. I want to dig into this for just a few minutes." He thinks something already starts to tackle it, and he went to the marketing studio of a campaign record on his own screen, where you can add assets of every kind, marketing emails, SMS, meetings, one-to-one emails, scheduling pages, sequences, workflows. He had a name for the bundle. "Let's call them harnesses for email, shall we?" Oakes was not sold on the name, but he let it ride.
Chris's bigger point was about strategy before configuration. If the communication incoherence exists in a portal, which he says it almost always does, the first step is to step back and "document the communication strategy of the business, of who are we contacting, when, and for what reason, and who owns it?" The canvas is a way to see where the gaps are, even if you cannot edit it easily from that space. Then he named the request. "But email coherence in HubSpot, I think, is a fair request for this first refounding request."
Oakes gave it credit. "Directionally, I think you are right." He added an asterisk, which is that the campaign space is Pro only in the US for now, and locked for others until the pricing model changes roll out across all portals, and he has not seen a lot of adoption yet. What he wants beyond it is the business visible at a high level. "You can't rely on the data in the portal to tell you how the business runs or should run. That can be one witness." He told the story of a CEO who put up one slide that showed how a whole national company worked, and said a canvas like that could give Breeze or Claude the high level process they need.
Chris said HubSpot is getting close in a lot of places, and that work management can build some of this with the right visuals, though you cannot click into it and flow around. "We're getting so close all over HubSpot." He tied it to the cost side too. If you cannot explain your own communication strategy, "it might be hard to get coherence of what the word email means inside of your HubSpot portal." HubSpot will make it very easy to email however you want, "especially when it starts costing credits per email send."
Oakes had the last real line on it, and it is the one that stuck with me. "I don't think there should be types of emails. I think there's just emails and they are just part of the way that we communicate with customers." Chris wrapped it. "A fair request, I think."
The Close
Chris closed by letting everyone know I was out, and thanked Oakes and the co-hosts stepping in so the show keeps going. I am grateful to them for it. The three update pages are linked above if you want the details behind this morning.
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 on the next show.
Produced by Value-First Media
