Use Breeze Assistant in Slack to update records, workflow enrollment and much more
Monday, October 19, 2026
What it is
Breeze Assistant can now update CRM records, enroll records into workflows, help prep for meetings, log calls and more, all started from a Slack thread. It rolls out automatically: DM Breeze or @HubSpot (Breeze) in a channel. Bulk actions show a confirmation card listing every affected record before anything is written. Live as of October 19, 2026, for all hubs and tiers.
Why it matters
Per HubSpot, dedupes, bulk reassignments and workflow enrollments are recurring data-quality and ops jobs that used to mean leaving Slack and taking several steps in HubSpot. This gives a faster, trustworthy way to make changes where the conversation is happening.
The Take
Breeze in Slack has the awareness that Breeze in HubSpot would, which is like, oh, I'm not supposed to just blanket reassign deals with companies because there's these rules and there's automations that back them…
The part of this I went looking for was permissions. It is not explicitly called out, but from historical patterns I have to conclude these will all be user permission gated. When I see "enroll this contact into workflow" or "reassign all of Sarah's accounts to Mike," I think, okay, that is going to be a problem if it is not. Casey's guess was the same shape: only if you have Slack connected and your user has access to those permissions. Neither of us read that off the page, so treat it as a read, not a fact.
Casey named the pattern: people using HubSpot but not necessarily in HubSpot. I am curious to see how that evolves. Here is where it lands for me. Something I am doing with clients is encouraging them, not terribly successfully, frankly, to get the things they put together into Breeze context, whether that is a knowledge vault or just the overall AI context. For whatever reason, October has turned out to be the month of sales territory, record ownership and reassignment on a bunch of projects for me. If you have territory assignment rules, it is not just what region they are in. There are all kinds of other parameters, specialties and so on. This is where you want that documented, hopefully, so we get to a point where Breeze in Slack has the awareness that Breeze in HubSpot would: I am not supposed to just blanket reassign deals with companies, because there are rules and automations that back them, and governance.
Chris put it well: this is the moment where agents are going to shine. AI has made it very easy to access systems of data from anywhere else, but editing a ticket record from Slack is different than asking the agent to make the updates. And if you put the effort into granular user permissioning on the HubSpot side, bringing Breeze into it is a completely different flow.
Who should act this week: anyone who does bulk reassignments or workflow enrollments, and the first step is writing your rules into Breeze context, not turning the Slack path loose. Who can wait: teams not using the Slack connection.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
How do I use it?
Per HubSpot, it rolls out automatically. DM Breeze, or @HubSpot (Breeze) in a channel, and start from a Slack thread.
What can it do?
Per HubSpot, update CRM records, enroll records into workflows, help prep for meetings, log calls and more.
Is there a safety check on bulk changes?
Per HubSpot, bulk actions show a confirmation card listing every affected record before anything is written.
Is it permission gated?
The page does not explicitly say. Joshua Oakes concluded from historical patterns that these actions will be user permission gated, and Casey Hawkins guessed it applies only if Slack is connected and your user has access to those permissions. Both are reads, not confirmed facts.
What should I do before I use it for bulk reassignments?
Joshua Oakes' practice with clients is to get territory and ownership rules documented into Breeze context, such as a knowledge vault, so Breeze in Slack knows not to blanket-reassign. Chris Carolan added that granular user permissioning on the HubSpot side matters more once Breeze can act from Slack.
Produced by Value-First Media