HubSpot's developer platform has had a busy year, and if you only follow the highlight reel, you've probably missed most of it. The flashy stuff gets a press release; the tools that actually change your day-to-day as a developer usually show up buried in a monthly changelog nobody reads end to end.
I went through this year's best updates from HubSpot, so you don't have to. Here are seven releases from 2026 that are actually worth your time, and why.
1. App Pages
You can finally build a real app, not just a card.
For as long as I can remember, a custom HubSpot app meant one card, crammed into a sidebar, doing its best impression of a full application. That's changed.
App Pages, which came out with the Spring 2026 platform release, lets you build actual multi-page experiences in React, with PageRoutes and PageLink for navigation and a PageHeader for page-level actions. If you've ever tried to force a multi-step workflow into a 300px-wide card, you know exactly why this matters.
2. Serverless Functions
They are back, and this time, they're tiered.
Quick bit of history: App Functions, HubSpot's serverless layer, quietly disappeared on platform version 2025.2. Not deprecated with fanfare, just... gone.
They're back on 2026.03, and this time with three access tiers: private functions for Enterprise or developer test accounts, public endpoint functions for Content Hub Enterprise, and a proper way to test in a sandbox before you touch production.
They also hook straight into UI Extensions, App Cards, Settings pages, and the new App Pages, so you're not stitching together a separate backend just to add logic to your app.
3. useCrmSearch
A hook that should've existed years ago.
This one's small but I like it: useCrmSearch is a React hook for UI Extensions that searches CRM objects, contacts, companies, deals, tickets, custom objects, with either free text or structured filters.
No more writing the same search wrapper for the third time. If you've built more than one CRM-aware extension, you'll recognize the boilerplate this quietly kills.
4. AI-Created Workflows
Breeze will write your workflow code, and then let you fix it.
Breeze, HubSpot's AI assistant, picked up the ability to generate custom code workflow actions in May, meaning it handles the input definitions, the logic, and the outputs, then hands the result to you to review and edit before saving.
The important part isn't that AI wrote it. It's that you still have to look at it before it ships. That's a very different tool than one you're expected to just trust.
5. Webhooks Journal API
It finally stopped being the bottleneck.
If you've run an integration at any real scale, you've probably hit the point where webhook volume outpaces your ability to process it. This update goes right at that: batched reads (up to 100 entries per call), CRM object filtering on subscriptions so you're not drowning in events you don't care about, list membership subscriptions, and snapshot status polling for async jobs.
None of this is glamorous. All of it is the difference between an integration that keeps up and one that quietly falls behind.
6. Improved Command-Line Interface
The CLI stopped assuming you only have one client.
Anyone managing more than one HubSpot portal has, at some point, deployed to the wrong account. The CLI now stores credentials centrally (~/.hscli/config.yml), links accounts per project directory with hs account link/unlink, supports NPM workspaces, and ships a new hs app logs command that pulls logs across functions, CRM cards, webhooks, and API calls, with --tail support.
If you work at an agency, this alone might save you from a bad afternoon.
7. New MCP Servers
Two MCP servers, doing two very different jobs.
This is the one to actually pay attention to, even if you're not touching it yet. HubSpot's remote MCP Server went GA in the spring: it gives an AI agent read access to campaigns, pages, and blog content, and write access to CRM objects, later extended to landing pages and page-level analytics.
Separately, there's a local Developer MCP Server built for a different audience, developers who'd rather describe what they want in plain language, inside something like Claude Code or Cursor, and let the platform's conventions handle the scaffolding.
One is for agents that touch your data. The other is for agents that help you build. Try the second one on something low-stakes before you bet client work on it.
Where to Start
None of this needs to happen at once. If your team keeps jamming multi-step workflows into a single sidebar card, App Pages solves that directly. If CRM lookups are eating more of your day than they should, useCrmSearch is worth a look. If you're juggling more than one client portal, the CLI changes alone are probably worth the update.
The rest, functions, webhooks, the MCP servers, are worth knowing exist so they're not a surprise the day a project actually calls for them.
If any of these updates are already creating friction in your team’s day-to-day, or you’re not sure which ones are worth acting on first, let’s talk. We help teams turn HubSpot platform changes into practical builds, cleaner implementations, and fewer avoidable mistakes across client portals.
Contact us today to talk through what’s changed, what matters for your setup, and where it makes sense to start.
You might also be interested in:
.svg)
Contact Us
.jpg)