Skip to content

Choose a plan for your HubSpot workflows.

Start with 1,000 free credits. Choose a monthly plan when you're ready to run more workflows. Prices are in USD.

Free

Build and test your first action.

$0

1,000 credits, one-time

1,000 runs at 2 seconds each

At 1 vCPU and 512 MiB RAM. Shorter runs use fewer credits; longer runs and larger machines use more.

No monthly refill.

Start building
  • Max runtime: 5 minutes
  • Memory: 1 GiB
  • CPU: 2 vCPUs
  • Build time: 10 minutes, lifetime
  • Simultaneous executions: 1
  • Connected portals: 1
  • Team members: 1
  • Run history: 7 days
  • Support: Documentation/community

Tests and previews share your credits. Upgrade when they run out.

For growing workflows

Pro

Run your team's daily workflows.

$99/month

25,000 credits per month

25,000 runs at 2 seconds each

At 1 vCPU and 512 MiB RAM. Shorter runs use fewer credits; longer runs and larger machines use more.

Credits reset each billing month. No rollover.

Choose Pro
  • Max runtime: 30 minutes
  • Memory: 4 GiB
  • CPU: 4 vCPUs
  • Build time: 100 minutes per billing month
  • Simultaneous executions: 10
  • Connected portals: 3
  • Team members: 5
  • Run history: 30 days
  • Support: Email

Additional usage: $5 per 1,000 credits, prorated on your monthly invoice.

Scale

Handle more workflows across portals.

$349/month

100,000 credits per month

100,000 runs at 2 seconds each

At 1 vCPU and 512 MiB RAM. Shorter runs use fewer credits; longer runs and larger machines use more.

Credits reset each billing month. No rollover.

Choose Scale
  • Max runtime: 2 hours
  • Memory: 8 GiB
  • CPU: 8 vCPUs
  • Build time: 500 minutes per billing month
  • Simultaneous executions: 25
  • Connected portals: 10
  • Team members: 15
  • Run history: 90 days
  • Support: Priority email

Additional usage: $5 per 1,000 credits, prorated on your monthly invoice.

Every plan includes JavaScript and Python, compatible npm and Python packages, draft testing, published builds, secrets and execution isolation. All connected portals share the workspace credit wallet.

How execution credits work.

Credits cover a start charge plus the time your code runs, at the CPU and memory you allocate. Waiting for an API counts; waiting in the queue does not.

1-second run

0.845 credits

2-second run

1.000 credits

3-second run

1.155 credits

10-second run

2.241 credits

Examples use 1 vCPU and 512 MiB RAM and are rounded to three decimal places. Fractional credits are retained; there is no one-credit minimum.

No Data Hub Pro upgrade for Turbyn’s code action. Appropriate HubSpot workflow access is still required.

Execution credits

8,420 / 25,000

Example monthly credit usage · Pro

Additional usage is $5 per 1,000 credits, prorated on your monthly invoice. Included credits reset each billing month without rollover.

View usage
Start charges and execution rates
Credit rates for default and maximum resource allocations
AllocationCPU / RAMStart chargePer second
Default on every plan1 vCPU / 512 MiB0.6897530.155123
Free maximum2 vCPU / 1 GiB0.8130930.216793
Pro maximum4 vCPU / 4 GiB1.1280830.374288
Scale maximum8 vCPU / 8 GiB1.6897530.655123

Rates are in credits, rounded to six decimal places. Execution usage equals the start charge plus runner seconds multiplied by the per-second rate. Maximum allocations are plan ceilings; every plan defaults to 1 vCPU and 512 MiB RAM.

Questions about plans and credits.

No. One two-second execution at 1 vCPU and 512 MiB RAM uses one credit. Usage combines a resource-dependent start charge with a per-second rate. Shorter runs can use less than one credit; longer runs and larger machines use more. The run counts on the cards are reference equivalents, not fixed run allowances.