What can custom coded actions do in HubSpot workflows?

What this bundle builds

Eighty specs that all share one thing: a step where the native action list runs out and you write code instead. They come from the four jobs that keep hitting that wall. Turning free text into one standard value, because a lookup table of country spellings cannot live in a branch. Reading the records associated to the enrolled one, because a deal cannot see its own line items. Talking to something outside the portal, because there is no native action for your product API. And doing arithmetic, because a workflow branch compares two properties but never subtracts one from the other.

This suits an in-house operations owner who already has Data Hub and is not sure what it actually buys them, and an agency that keeps rewriting the same domain matching code on every portal. The five components map to the five shapes that code takes in a workflow: transformation and formatting, cross-object lookups and associations, external APIs and webhooks, scheduling and date math, then scoring and calculations. Every spec names its secrets, its input fields and its output fields before the first line of code.

How the pieces fit together

Start with the formatting specs. They need no token, no secret and no API call, so you can build one in twenty minutes and see the pattern: inputs in, lookup table, output fields, error branch. That build teaches you the shape of every other spec in the pack.

Cross-object work comes next, because it adds the first dependency: a private app token with read access on the objects you search. Company association from email domain is the one to build first, since duplicate detection, the line item check and the association caps all reuse its search and its free-mail exclusion list.

External calls come third, once you have somewhere safe to keep a secret and a convention for failure. Scheduling sits fourth: it reuses the earlier code but multiplies the execution count, which is where rate limits start to bite. Scoring comes last because a score is only as honest as the properties feeding it, and those properties are what the first three components clean up.

What you get

• 80 specs, each with outcome, prerequisites, enrollment, steps, known pitfalls, a test plan and variants
• Each spec ships as PDF and Markdown
• Properties JSON, 125 properties across contacts, companies, deals, tickets, products and nine custom objects
• Workflow JSON for all 80, in Automation API format, switched off on import
• 80 custom coded actions as JavaScript files, each with its inputs, outputs and secrets named in the header
• A test plan per spec, including the forced-failure step that proves the error path works
• Install in one click for Full and Agency buyers

Who it is for, and who should skip it

Buy this if your portal already has Data Hub Professional or Enterprise and the licence is underused, or if you build on client portals and keep rewriting the same normalization and matching code. You get value in the first hour from the formatting specs alone.

Skip it if you do not have Data Hub. Nothing here runs without the custom code action, and buying it to find out is an expensive way to read a tier table. Take the native-only bundle instead. Skip it too if you want one specific outcome rather than a toolkit: a single bundle, or the full library, will fit better than eighty specs you did not ask for.