u/Agile-Pension4568

Restore CRM Changes lets you pick Integration as the source now. So when an integration writes bad data you can roll back just that app's changes instead of a broad restore that reverts everything else from the same window too. Enterprise, public beta.

Up to now if a sync or a private app messed up a bunch of records, you either did the source-blind restore (and reverted unrelated stuff along with it) or you exported the property history and re-imported the old values, which is about as tedious as it sounds. The per-record Undo doesn't work on connected app or API changes at all, so that was never on the table for integration writes anyway.

The source list includes MCP connectors now too, Claude's in there. Probably the part I'd watch, since a lot of people are starting to let agents write straight to the CRM and an agent doing the wrong thing quickly is just the import problem again with extra steps. Being able to undo one source without touching the rest helps.

Say a Salesforce sync misfires and overwrites lifecycle stage on a few thousand contacts. You can now pull back just that sync's writes from the window.

One thing I can't tell from the release notes: it's described as property changes, but the restore tool also has a separate Created records type. Anyone in the beta know if the Integration filter covers both, or just modified properties? Wondering what happens with an integration that created and updated records in the same run.

Revenue Hub launched and half the comments I'm seeing are some version of "oh, Commerce Hub with a new name." I get why, the marketing doesn't help, but that take misses what actually changed.

The actual change isn't one new feature, it's that quoting, contracts, billing, payments and renewals run off the same chain inside the CRM now, instead of four tools you stitch together by hand. If you've run recurring revenue in HubSpot you know the old setup: quote in one place, contract in a folder somewhere, finance rebuilding the invoice by hand, and by renewal nobody's totally sure what the customer is even paying for.

The thing that makes the chain actually hold together is the Contracts object. It's a proper CRM object now, like contacts or deals. Accept a quote and a contract gets created automatically with the term dates, MRR/ARR, line items, all of it. Someone adds seats mid-term, you spin a change quote off the contract and it handles the proration. Renewals pull the current products off the existing contract so you're not rebuilding anything from scratch. Basically the glue that was always missing.

Worth saying though, none of this rescues you from setup. The contract just inherits whatever's in the quote, so if your product library and pricing rules are a mess, congrats, now the mess moves downstream automatically. CPQ's only as good as what's under it.

Also, for anyone not in the US, before you get excited or annoyed: HubSpot Payments is US/UK/Canada only. Everywhere Stripe operates you collect through Stripe, so payments aren't off the table outside those three. If you're billing into the EU, the part worth scoping is e-invoicing. The card flow is the easy bit.

Anyway. Anyone actually moved quoting and contracts into HubSpot yet, or is your billing stack too embedded to bother?

HubSpot partner here, so factor that in.

Pipeline rules are coming to contact and company lifecycle stages. In public beta now, supposedly going GA around 29 June. Basically the same rules deals and tickets already had, finally on contacts and companies.

Three of them, under Settings > Objects > Contacts (or Companies) > Lifecycle stages > Pipeline Rules:

• Limit contact creation to specific stages (you can also set a default creation stage)
• Restrict contacts from skipping stages
• Restrict contacts from moving backwards

The creation limit is the one I'd switch on first. Right now nothing stops someone importing a list of event badge scans straight in as MQL, and then your funnel looks great for a week while your conversion rates turn to garbage. Skipping and backwards matter too, but the only real protection lifecycle stage ever had was that automation won't set it backwards, and everyone gets around that by clearing the value first anyway, so it never did much.

Caveat that's going to come up in the comments before I even finish typing this: per the beta UI, Super Admins, anyone with permission to edit property settings, and pipeline automations can bypass all of it. So it's not a hard lock. It stops normal users doing normal-user things. If your mess is being made by an admin or a workflow, this isn't your fix.

Anyone in the beta already turned the creation limit on? Wondering whether it plays nicely with imports and integrations or just throws errors everywhere.

Saw this in HubSpot product updates this week. They've added an AI quality check inside the email editor — grammar, spam triggers, broken links, missing token fallbacks. Standard stuff.

But one of the checks scans how AI inbox assistants will summarize your email to the recipient.

That one stopped me.

More and more inboxes are running Gemini or Apple Intelligence. The AI writes a summary that sits at the top, and for a lot of recipients, that summary IS the email. Whether they open it or not is downstream of that.

We've been talking about AEO and GEO for search. This is the same problem inside the inbox. There's now an AI between me and my reader making editorial decisions about my email before my reader sees a word of it.

So now I'm writing for a human, a spam filter, and an AI summarizer. The summarizer is the new one and I have no idea how to think about it yet.

Writing for the AI feels gross. Like writing meta descriptions for Google in 2008. But ignoring it means a chunk of my list reads whatever Gemini boils my email down to, not what I actually wrote.

Are you adjusting your email copy for this? Or pretending it's not happening yet?

HubSpot partner here so factor that in.

Did anyone else clock the intelligence layer paragraph in HubSpot's open-ecosystem post? It's the bit in the middle where they say they're exposing deal risk, benchmarks, and patterns drawn from 280K+ portals as an API. For anyone building on top.

Reason I'm asking: that paragraph is a real chunk of what senior RevOps consultants get paid for. Pipeline diagnostics, deal risk flagging, conversion benchmarks based on comparable companies. That work's been billable for years because it's hard. If it ends up being a function call... that's a shift. Not in 5 years. Sooner.

The part that's nagging at me though is whether anyone's CRM is actually ready for that. Most portals I touch in audits, the custom properties don't have descriptions. The ones that do say things like "custom field" or "do not use." Workflows are named "Workflow 47." Lifecycle stages have no documented transition rules.

Agents reasoning over that mess will start making stuff up. And when they do, it's not "oh well try again," it's your customer-facing automation confidently saying something that isn't true to a real human.

I don't see agent-readiness being talked about as a portal-quality thing yet. Most conversations are still about AI features the platform offers, not whether your data is in a state where an agent can do anything useful with it. Which feels backwards.

Anyone here running any kind of pre-flight before plugging Breeze / Claude / GPT / whatever into a portal? Or just wiring it up and hoping for the best?

Hubspot quietly shipped a Tasks rebuild in Public Betas and I'm actually impressed. Tasks now work the same way as the rest of the CRM — same view types (table, board, Gantt, calendar), same filtering, same patterns you already use on Deals and Companies.

Disclosure since it's relevant: I run a Hubspot partner agency, so I see this across a bunch of portals.

The two views I'm getting the most out of are Gantt and Calendar. Calendar is great for weekly planning — same data as a list, but my week makes more sense to me as a grid. Gantt I'm using for the in-between stuff: customer renewals coming up, content cycles, internal initiatives that have a deadline and a sequence but aren't full implementations. The meeting note taker auto-creates tasks from calls and they finally have somewhere usable to live.

Implementation work still goes in Projects for us. But the Tasks Gantt and the Projects timeline look almost identical now, which is probably going to confuse a lot of teams about which tool to use for what. I'm splitting it like this: Projects for delivery work with phases and dependencies (implementations, big rollouts), Tasks for everything else with a deadline. Not sure if that holds up long term.

Where are other people drawing the Tasks vs Projects line now that the views overlap so much?

And are the new filters holding up for your team's workflows, or are you hitting limits already?

Let’s face it, creating properties in HubSpot is tedious and boring. The whole form for every property, one at a time, and if it’s a dropdown you also get to add every option by hand. Fine when you have 3 to create, a lot less fine when you have 30.

I spent half a day on this for a project earlier this week and around property 14 I just gave up and wrote a small script that reads a file and creates them all through the API. Took an afternoon to put together and did the same job in a few minutes.

I know HubSpot’s import tool will create properties on the fly from a spreadsheet, but that only works if the source file is actually clean, which in my experience is almost never.

Not sure if this is obvious stuff everyone here is already doing or not.