Skip to content
Bryant WorksBook a Call

HubSpot custom development guide

Should you use HubSpot custom code actions?

Chris Bryant, Founder

Updated Nov 2026

Use HubSpot custom code actions when a workflow cannot finish a job with its standard actions, such as deduplicating records or calling an LLM API. Keep standard actions for jobs they cover. Choose an integration when data moves between systems on a schedule. Rank each job by time saved and errors reduced, and build the top one first.

Book a Call
  • HubSpot Diamond Partner
  • 660+ client organizations
  • 330+ five-star reviews

Every HubSpot portal collects jobs that its workflows get close to and then drop. Phone numbers arrive in mixed formats, and renewals need a copy of last year’s deal. Your team fixes these by hand, and each manual fix adds errors of its own. The choice in front of you is which of 3 tools takes the job, and who maintains it after launch.

Who faces the custom code decision

The decision lands on the person who owns the portal, such as an ops or RevOps lead. That person also owns whatever breaks after the build ships. These signs show the decision has arrived:

  • Someone exports records to a spreadsheet each week, fixes values and imports them back.
  • Reps copy deals or tickets by hand when a renewal or a new phase starts.
  • Calls reach the wrong person because the routing rule depends on logic no workflow action covers.
  • Marketing wants AI summaries or scores written onto records.
  • Duplicate records split the activity history between 2 versions of one contact.

Each sign points to a job the portal could run on its own. The open question is which tool runs it and who keeps it working.

Criteria for standard actions, custom code or an integration

Weigh every candidate job against the same 5 criteria. The table gives a short reading of each option against each one.

Criterion Standard actions Custom code action Integration or app
Best fit Logic the built-in actions cover Logic on one record at a time Data moving between systems
Who can change it Any trained admin Someone who reads code A developer or the vendor
Typical time to deploy Days for a single workflow Days for a single workflow 1 to 3 weeks for one well-documented API
What breaks it A renamed property or option A property change or an API change A change in either system
Upkeep Admin review A named owner for the code, plus documentation Monitoring and an owner per system

The time figures are our typical ranges. An integration build-out across several platforms takes 4 to 8 weeks. Read the criteria in order for each job. The first criterion that rules out an option settles that option for that job.

Standard actions

Standard actions win on upkeep. Any admin you train can open the workflow, read each step and change it. Their limit sits in the logic they offer. Once a job needs logic that no built-in action provides, the workflow stops short and someone finishes the job by hand.

Custom code actions

A custom code action runs as a step in the workflow, so the trigger stays where your team already looks. It handles logic the built-in actions lack, and it can call an outside API. The cost is upkeep. Someone who reads code has to own it, and a property rename can stop it.

Integrations and apps

An integration moves data between HubSpot and another system on its own schedule. It suits jobs that span systems or run on large volumes. It takes the longest to build of the 3 options and needs monitoring on both sides.

Jobs custom code actions handle well

Our custom code automation work covers jobs that workflows can’t do alone, including these:

  • Normalization. The action rewrites values such as phone numbers or job titles into one format, so lists and reports group them correctly.
  • Record cloning. The action copies a record and the fields your team needs when a renewal or a new phase starts.
  • Call routing. The action assigns a call to the right owner using rules your team defines.
  • Deduplication. The action finds records that match on your rules and flags or merges them.
  • LLM calls. The action sends record data to an LLM API and writes a summary or a score back to a property.

Each of these jobs starts from one record and writes a result back to it. That pattern fits a workflow step, because the trigger and the output sit on the same record.

Suppose, as an imagined case, your forms collect job titles as free text and your lead routing depends on seniority. Free text rarely matches a fixed list of values. A custom code action can read the title, map it to a seniority band and write that band to a property. Your routing workflow then branches on the clean property.

AI steps follow the same order as the rest of the portal. Our approach puts clean data and a working process ahead of any AI step. An LLM call on inconsistent records returns inconsistent answers. We test every AI feature and agent before it touches live data, and each AI result gets a human review before it reaches a client’s portal.

When an integration or app fits better

A workflow step starts from the record that triggered it. Some jobs outgrow that unit of work. An integration or a standalone app fits better under these conditions:

  • Data moves between HubSpot and another system on a schedule.
  • Several systems need the same record kept in step.
  • The job processes large volumes in one pass, such as a history backfill.
  • Your team needs a button or an export to act on the result.

One client, an agency in commercial insurance, shows the first condition. Our custom sync moves its AMS360 quotes and policies into HubSpot every 20 minutes, along with contacts. Some objects sync both ways, and others update on triggers. That job runs on a clock and spans 2 systems, so it belongs in an integration.

RoadRunner shows the volume condition. A suite of AI agents that we built and host outside HubSpot reads about 4,000 customer emails a day for churn signals. The suite costs about $12 a day to run. Over its first 2 months, we recorded $100K+ MRR identified and potentially saved.

Other jobs need a tool your team uses directly. We have built small tools for HubSpot such as these:

  • A one-click export of a record to PDF.
  • Labels for return shipping, created from a record.
  • Importers that format and load CSV files sent by FTP or email.

For each connection, we choose one of 3 build types:

  • A native connector.
  • Third-party middleware.
  • A custom build.

Data volume and sync frequency drive the choice, along with the upkeep each option needs. Before we build anything new, we audit your existing integrations for gaps and silent failures. Before any integration goes live, its data flow runs through a staging environment for validation.

Ownership and maintenance after launch

A custom code action is software inside your portal. It needs an owner the day it ships. Property renames and expired API credentials can each stop it. Before launch, put these in place:

  • A named owner who can read the code and change it.
  • A written note for each action that lists the properties it reads and writes.
  • A small set of test records to rerun after any property change.
  • A review date for the credentials of every outside API the code calls.

Each implementation we deliver closes with notes on what we built and the reason for each piece. Our training engagements add recorded walk-throughs and written guides for later hires. Those records let a new admin trace an action back to the job it serves.

When no one on your team reads code, a retainer can cover the upkeep. Our pricing page lists 2 retainers for ongoing work.

Plan Monthly fee Hours included Overage rate Response
Growth Ops $3,000 15 $200 an hour Email response within 24 hours
Priority Ops $4,750 25 $190 an hour Same-day response

Both retainers carry a 3-month minimum. After it, you can pause or end a retainer with 30 days’ notice. Defined builds run at our project rate of $225 an hour, with a 10-hour minimum for new clients.

Conditions that tip the choice

Some jobs sit between 2 columns of the criteria table. These conditions settle the close calls:

  • The logic fits built-in actions. Keep it in standard actions, because any admin can maintain it.
  • The job repeats on every record of one type. A custom code action fits, triggered by the same event each time.
  • The data lives in another system. Build an integration, and keep code actions for cleanup after the data lands.
  • No one on staff reads code. Build only with a retainer or a trained owner in place.
  • The output comes from an LLM. Plan a review step before the result drives routing or outreach.
  • The job is outreach a rep sends to one contact. Our guide on sequences versus workflows covers that choice.

This guide states no tier requirements or runtime limits for custom code actions, because those come from HubSpot’s own documentation. Check that documentation for your portal before you scope a build.

We rank automation opportunities by time saved and errors reduced, then build the highest-ranked first. A single workflow can deploy in days. Auditing and building out your automations in full typically takes 3 to 6 weeks.

Start your own ranking with a list of the manual fixes your team repeats each week. Next to each fix, note who does it and what goes wrong when it slips. The top item on that list becomes your first custom code action or your first integration.

Common questions

What are HubSpot custom code actions?

Custom code actions are workflow steps that run code your team or a partner writes. They handle jobs the built-in actions can't do alone, such as normalizing values or deduplicating records. We also build custom code actions that call LLM APIs and write the result back to a record.

How do you add custom code to a HubSpot workflow?

You add it as a custom code action inside the workflow, at the point where the built-in actions stop short. Before you write it, list the records the action reads and the properties it writes. Test it against a small set of sample records before the workflow goes live. Name an owner who can read and change the code after launch.

When should you hire a HubSpot automation consultant?

Hire one when your team repeats manual fixes that workflows can't finish and nobody on staff reads code. A consultant ranks those fixes and builds the ones that save the most time first. At Bryant Works, a single workflow can deploy in days, and auditing and building out your automations in full typically takes 3 to 6 weeks. Our project rate is $225 an hour, with a 10-hour minimum for new clients.

Can HubSpot workflows call an external API?

Yes, a custom code action inside a workflow can call an external API. We have built custom code actions that call LLM APIs and write the response back to a record. The API needs credentials, and someone must renew them before they expire. For jobs that move data between systems on a schedule, an integration fits better.

Let's scope it together.