HubSpot Workflow APIs: A Practical Guide to Automating Your CRM
Most CRMs keep their automation locked behind a drag-and-drop editor and a support queue. The hubspot workflow apis hand you the keys instead. You can reach into your automations, build them in code, and wire them to every other tool your business runs. No support ticket. No agency invoice. Just code you own.
Ever hit the wall where a HubSpot workflow could almost do what you need, if only the visual editor let you push one step further? This is how you get past it. And the door is wider than most people think. Here is what these APIs really do, where they turn genuinely powerful, and the traps worth knowing before you write a line.
What the HubSpot workflow APIs actually do
Plain version first. The HubSpot workflow APIs let you create, read, update, and delete workflows without ever opening the visual editor. You will be working with the v4 automation API, and it treats your automations as data. Fetch it, change it, push it back.
Why bother? A few reasons that come up constantly. You are running dozens of near-identical workflows across regions or product lines, and editing each one by hand is a Tuesday you will never get back. You want your automation logic under version control, the same way your app code is. Or you are building an integration that has to spin up a fresh workflow for every new customer account, automatically, forever.
That is the shift. The hubspot workflow apis turn automation from something you click into something you build, deploy, and repeat. And the bigger your operation gets, the more that matters.
While you are here, how do your reviews compare?
Type your business name and see where you rank against your competitors. Free, no signup.
Trophy Jar asks every customer for a review automatically, from $9 a month.Start now
The three building blocks behind hubspot workflow apis
Everything you touch through the API breaks down into three pieces: triggers, actions, and data outputs. Get these three straight and the rest is just detail.
Triggers decide when a workflow fires. A record hits your enrollment criteria (a deal moves to closed-won, a contact submits a form, a property changes) and the automation starts. Actions are what happens next. Send an email. Update a property. Create a task. Call out to another system. Data outputs are the values those actions produce and pass down the line to whatever runs after them.
Here is the nice part. Those same three concepts hold whether you are building a two-step welcome sequence or a fifty-step revenue engine. The hubspot workflow apis never make you learn a second mental model. You are always describing the same thing: what starts it, what it does, what it hands off.
Custom code actions: where hubspot workflow apis get powerful
This is the part people fall for. Inside a workflow you can drop a custom code action and write real logic, in JavaScript or Python, that runs right there in the flow. Need to hit an external API, reshape some data, or run a calculation HubSpot has no native action for? Write it once. It just runs.
Two limits are worth committing to memory. A custom code action has to finish inside 20 seconds, and it can use no more than 128 MB of memory. Heavier than that and you hit a wall. The standard move is to push the real work to something like AWS Lambda, run it asynchronously, and call back to HubSpot to mark the action complete when the job is done.
One catch on pricing. Custom code actions live on the Professional and Enterprise tiers of Data Hub, the product HubSpot used to call Operations Hub. They are not on the starter plans. Check your subscription before you architect around them, because nothing stings quite like designing a system your plan cannot run. Paired with the hubspot workflow apis, custom code is what lets a workflow reach anywhere your business needs it to go.
Webhooks and custom workflow actions
Sometimes you do not want to write any code inside HubSpot. You just want the workflow to tell another system that something happened. That is what webhooks are for.
You get two routes. There is the built-in Send a webhook action (Data Hub Professional and Enterprise), which fires an HTTPS request to a URL you pick the moment the workflow reaches that step. And there is the Webhooks API for developer apps, for when you are building something more permanent. Either way the endpoint has to be HTTPS, and you can lock it down with a request signature or an API key so you know the call actually came from HubSpot and not someone poking at your URL.
Then there are custom workflow actions. These are reusable, app-based extensions that connect a workflow to an outside service through a pre-configured action URL. Build one properly and a non-technical teammate can drag it into any workflow like it shipped with the product. This is how most App Marketplace integrations plug into the hubspot workflow apis, and it is exactly why a good one feels like part of HubSpot instead of a bolt-on.
What changed for hubspot workflow apis in 2026
Two things landed this year that change how you plan. Both are good news, which is not something I say about API changes very often.
First, HubSpot moved to date-based API versions. The first one, 2026-03, is live. Breaking changes now arrive on a schedule, every March and September, each version is supported for at least 18 months, and versions are immutable once released. Translation: an integration will not break out from under you mid-window. If you have ever been burned by a silent API change on a Friday afternoon, you know exactly why that matters.
Second, the quiet one. Admins can now create Service Keys directly in HubSpot, no developer required. It is a lighter way to authenticate against the hubspot workflow apis when you do not need the full weight of a private app. For a small team that just wants to script a few things, that removes a real barrier. It is still in beta as of this year, so read the fine print before you bet a production system on it.
A word of caution before you build
The hubspot workflow apis are powerful, and powerful things tend to fail loudly. A few habits will save you a bad week.
Test your enrollment criteria on a tiny segment before you let a workflow loose on your whole database. Log what your custom code does, because a silent 20-second timeout is a miserable thing to debug once you are running at scale. And keep a written record of which workflows the API created, so a teammate six months from now is not staring at automations that seem to have appeared out of thin air.
Do this well and you get automation that scales with you instead of against you. If you are thinking about your broader stack, it is worth seeing how automated review collection fits the same operations-first mindset. The best systems all share one trait: they run without a human clicking the button every single time.
Reviews increasingly shape which businesses buyers and search engines trust. For context, see Google’s guidelines on reviews.
Automate the one workflow most teams still do by hand
Here is one you can automate the day your workflows are humming: asking for reviews. Most teams still treat review collection as a manual afterthought. Someone remembers to email a happy customer three days late, if at all. It does not have to work that way. The same operations-first thinking behind the hubspot workflow apis (a trigger fires, an action runs, nobody in the loop) applies perfectly to social proof.
When a deal hits closed-won in HubSpot, that is the exact moment your customer is happiest and most likely to say something kind about you. Wire that trigger to a review request and a milestone you already track turns into a steady stream of fresh 5-star reviews. Smart follow-ups nudge the people who have not replied yet, and only them, so nobody feels pestered.
That is the whole job of Trophy Jar. It plugs into HubSpot and the rest of your stack, sends the review request automatically the moment the trigger fires, and puts the reviews where they earn their keep: your website, Google, or a directory. Your automation should be collecting proof while it works, not just shuffling records around. Trophy Jar is the piece that does it.
Frequently Asked Questions
What can you actually do with the HubSpot workflow APIs?
You can create, read, update, and delete workflows programmatically with the v4 automation API, instead of building each one by hand in the visual editor. That opens up managing large numbers of similar workflows, keeping your automation logic under version control, and spinning up new workflows automatically as part of an integration.
Do I need a paid plan to use custom code actions?
Yes. Custom code actions, where you write JavaScript or Python inside a workflow, require the Professional or Enterprise tier of Data Hub (formerly Operations Hub). They are not available on starter plans, so confirm your subscription before you design around them.
What are the limits on a custom code action?
Each custom code action has to finish within 20 seconds and can use up to 128 MB of memory. For anything heavier, run the work asynchronously (on AWS Lambda, for example) and call back to HubSpot to mark the action complete when it finishes.
The bottom line on hubspot workflow apis
If there is one thing to take away about hubspot workflow apis, it is that consistency wins. The businesses that get the most out of hubspot workflow apis make it a steady habit, not a one-off push.
Related reading
Keep going: see automated review collection.
Turn a closed-won deal into a 5-star review, automatically
You already automate your HubSpot workflows. Let Trophy Jar automate review collection right alongside them, so every won deal becomes fresh social proof without anyone lifting a finger. Start for $9/month.