Home Install Documentation Changelog Support Marketplace Get Started
Pace Documentation

Everything you need to know about Pace.

From installation to advanced configuration. Complete guides on adding the Pace action to your workflows, how throttling works, plan limits, and troubleshooting — all in one place.

⚠ Important — Plan Limits: If you enroll more records than your daily plan limit, Pace does not hold those requests. They will be processed immediately by HubSpot unthrottled. Holding records beyond your plan limit would effectively provide unlimited throttling for free. Ensure your enrollment size stays within your plan's daily limit to keep all records throttled. View plan limits →

Pro tip: Add a Branch after the Pace action and choose "One property or action output" → set Pace Status = RATE_LIMITED to handle those records your way instead of letting them flow through unthrottled. See how →

Quick Navigation

Get started with Pace.

Quick Start

Install in 2 Minutes

Get Pace running from the HubSpot Marketplace, add the Pace action to your first workflow, and enrollments will start throttling automatically.

Get Started
Configuration

Pace Action Reference

How to add the Pace action, set batch size and delay, choose which workflows to throttle, and manage your active Pace actions.

View Action Docs
Calculator

Throttle Calculator

Enter your count, interval, and total records to see your throughput rate, completion time, and which plan you need.

Open Calculator
Documentation

Explore the guides.

Click any section below to expand. Use the quick navigation above to jump directly to a topic.

Getting started with Pace takes about 2 minutes. No custom code, no API keys, no workflow modifications required.

Step 1

Install from Marketplace

Click Install on the HubSpot Marketplace listing. You'll be taken to HubSpot's secure OAuth authorization page. Accept the permissions and Pace is connected to your portal instantly.

Step 2

Add the Pace Action

Inside your HubSpot workflow, add the Pace action. Set your batch size (enrollments per batch) and delay (time between batches). Each Pace action targets the workflow it lives in.

Step 3

Done — Pace Handles the Rest

Enable the workflow. Pace intercepts enrollments and releases them in controlled batches according to your configured settings. Your integrations stay healthy and your sequences feel intentional.

Pace workflow action configuration in HubSpot
Prerequisites
  • Active HubSpot account with Admin access
  • At least one active workflow to throttle
  • No code, API keys, or developer tools needed
After installation
  • Add the Pace action inside any HubSpot workflow
  • Free plan includes 200 daily paces — upgrade anytime
  • The Pace action can be enabled and disabled at any time

Pace is configured directly inside your HubSpot workflow as a custom action. Once installed, add the Pace action to any workflow and set three things:

Configuration Fields
  • Batch Size (1–100) — How many records to release per batch
  • Delay Amount — How long to wait between each batch
  • Time Unit — Seconds (10–300), Minutes (1–60), or Hours (1–12)
Things to know
  • Each Pace action targets the workflow it lives in
  • If the workflow is turned off, Pace still processes the queue and sends completion callbacks to HubSpot at your configured rate — but HubSpot may drop them if the workflow is inactive
  • Your daily pace limit applies across all active Pace actions
Good to know
  • Everything is configured directly in the Pace workflow action — no separate setup required
  • Changes take effect immediately — no need to re-enroll existing records
  • Use the Throttle Calculator to find the right settings for your enrollment size

Enter your settings below — the calculator shows completion time, throughput, and which Pace plan you need.

Pace Throttle Calculator
Completion Time:
Per Hour
Daily Paces Used
Plan Needed

Good starting points

For email sequences: 25 records, 10 minutes. For API integrations: 5–10 records, 5 minutes. For bulk data: 20 records, 5 minutes. For long-range nurture campaigns spread across months: 25 records, 1 week. You can always adjust the Pace action settings without stopping your workflow.

HubSpot workflows enroll all qualifying records at once by default. Pace sits between your workflow trigger and enrollment, queuing records and releasing them as controlled paces.

All enrollments wait their interval

Every enrollment — including the first — waits the full interval before going out. If your Pace action is set to 10 enrollments every 1 hour and you enroll 200, the first 10 paces wait 1 hour before going out, the next 10 wait another hour, and so on. No enrollment skips the queue.

Without Pace

Default HubSpot Behavior

When a workflow trigger fires, all matching records are enrolled simultaneously. 500 records trigger 500 simultaneous workflow executions — blasting your integration, API, or email provider at full speed.

With Pace

Controlled Pace Release

Pace intercepts the enrollments and places them in a managed queue. Every interval, Pace releases the next count enrollments into the workflow as a pace. The rest wait their turn — no data loss, no dropped records.

Why it matters

Protect Your Stack

Rate limits, API timeouts, email throttling, and integration overloads are all caused by sudden volume spikes. Pace smooths those spikes into a steady, predictable stream your tools can handle.

What happens when you hit your daily plan limit

If you exceed your daily plan limit, Pace returns a success response and those records continue through your workflow unthrottled — they will not be held or paced. Upgrade your plan or reduce your daily enrollment volume to keep all records throttled.

Pace enrollment logs showing RATE_LIMITED status and outputs

Pro Tip: Handle rate limited records with a branch

For maximum control over your workflow, add an if/then branch after the Pace action and filter on Pace Status = RATE_LIMITED. This lets you decide exactly what happens to records that exceed your plan limit — instead of letting them flow through unthrottled.

How to set it up:

  1. Add the Pace action to your workflow
  2. Add a Branch immediately after Pace — choose "One property or action output"
  3. Select "1. Throttle and queue workflow processing" as the action, then choose "Pace Status" as the output field
  4. Set the value to RATE_LIMITED
  5. On the RATE_LIMITED branch: end the workflow, send a notification, create a task — whatever makes sense for your use case
  6. On the None met branch: continue to your next workflow action normally

This setup is optional but recommended for high-volume enrollments where you want full visibility and control over rate limited records.

Pace RATE_LIMITED branch setup in HubSpot workflow

Record queuing and loss

Pace queues enrollments and processes them at your set rate — records are not dropped or skipped under normal operation. There is one exception: if HubSpot returns a 500 error on a completion callback, that record will be held by HubSpot for up to 7 days (HubSpot's maximum timeout) before being released from the workflow.

If the workflow is turned off, Pace still processes the queue and sends completion callbacks to HubSpot at your configured rate — but HubSpot may drop them if the workflow is inactive.

Pace solves a specific problem — uncontrolled enrollment volume. Here are the most common scenarios where Pace makes a real difference.

Email Sequences

Email Send Delays

Enrolling 1,000 records into an email workflow all at once can trigger spam filters and email provider rate limits. Pace spreads them out so your sequences land in inboxes, not spam folders.

Recommended: count 25–50, interval 10–15 minutes.

Integrations

API Rate Limiting

Third-party integrations (Slack, Salesforce, webhooks) have API rate limits. Mass workflow enrollments can hit those limits instantly and cause failed actions. Pace keeps your API calls under control.

Recommended: count 5–10, interval 5 minutes for most APIs.

Data Operations

Bulk Data Updates

Running a workflow that updates properties, creates associations, or writes to external systems on thousands of records can overload your stack. Pace keeps the volume predictable and manageable.

Recommended: count 10–20, interval 5 minutes for data-heavy workflows.

Pace plans are based on daily paces — the total number of enrollments Pace can release across all your active Pace actions in a single day.

Free — $0/mo

Free Forever

  • 200 daily paces
  • Smart Pacing Controls
  • All HubSpot Object Types
  • Batch Processing (1–100)
  • Flexible Delays
  • Email Support
Install Free
Starter — $29/mo

Starter

  • 5,000 daily paces
  • Smart Pacing Controls
  • All HubSpot Object Types
  • Batch Processing (1–100)
  • Flexible Delays
  • Email Support
Upgrade to Starter
Professional — $79/mo

Professional

  • 20,000 daily paces
  • Smart Pacing Controls
  • All HubSpot Object Types
  • Batch Processing (1–100)
  • Flexible Delays
  • Priority Support
Upgrade to Pro
Enterprise
Enterprise — $199/mo
  • 40,000 daily paces
  • Smart Pacing Controls
  • All HubSpot Object Types
  • Batch Processing (1–100)
  • Flexible Delays
  • Dedicated Support
What counts as a pace?
  • 1 pace = 1 record enrolled into Pace — counted when the record enters, not when it's released
  • You are not double counted — enrolling 200 records uses 200 daily paces. That's it.
  • The daily limit resets at midnight in your portal's timezone
  • Free plan: once the daily limit is reached, remaining records will flow through unthrottled

Approaching your daily limit?

When you reach your daily pace limit, any additional enrollment requests will be processed immediately by HubSpot rather than held. To avoid unthrottled processing, monitor your daily usage and upgrade your plan before you hit the limit.

Most Pace issues come down to one of a few root causes. Here's how to diagnose and fix the most common ones.

Issue

Enrollments Aren't Being Released

Check that the workflow is active and that you haven't hit your daily pace limit. Also verify the workflow is still turned on in HubSpot — Pace sends completion callbacks but HubSpot won't process them if the workflow is inactive.

Issue

Enrollments Are All Releasing at Once

This usually means your enrollment size exceeded your daily pace limit — records beyond your limit are passed through unthrottled. Make sure your enrollment size stays within your plan's daily limit.

Issue

Running Out of Daily Paces Too Fast

Review your active Pace actions and their batch size settings. High batch sizes deplete your daily limit quickly. Consider lowering batch sizes, upgrading your plan, or spreading enrollments across multiple days.

False Positive: "We didn't get a response from the connected app"

You may see this error in your workflow history. It looks like a failure, but it isn't — your record was still released correctly. Every record we queue is given its own scheduled release time directly in HubSpot, so if anything ever prevents us from confirming a release ourselves, HubSpot releases the record right on schedule automatically. This error just means HubSpot's own safety net did the releasing instead of us — nothing is missed, and no action is needed on your end.

Still stuck?

Our team built Pace and knows every edge case. Reach out directly — no ticket queues, no junior support staff. We'll get you sorted.

Every Pace release, logged. Newest at the top.

pace@solution-spot: ~/changelog — git log --releases
Live
$cat CHANGELOG.md
engine: dual-layer processing  |  queue: intelligent management  |  status: all systems nominal
v1.7.02026-07-20Latest
// Long-range scheduling & high-volume reliability
  • +New delay units: days and weeks. Pace a list out over weeks, not just minutes or hours.
  • +Per-record release times. Every record now shows its exact scheduled release inside HubSpot's workflow history — no more guessing where a contact sits in line.
  • +Independent branch handling. Workflows with multiple branches on different delay settings now run fully independently — each branch keeps its own schedule with no cross-contamination.
  • ~Built for scale. Large enrollments now process smoothly with no rate-limit errors, even under heavy simultaneous volume.
  • ~Stronger reliability. Every record carries its exact release time the moment it's queued, so a brief hiccup on our end never affects when your records go out.
  • !Delay handling refined across a range of enrollment patterns for more consistent, predictable releases.
  • Hardened long-horizon scheduling — delays are validated against platform limits before they're accepted.
v1.5.02026-06-20
// Smarter limits & clearer logs
  • +RATE_LIMITED branch output — filter records that exceed your daily plan limit and handle them your way.
  • +New enrollment logs view showing pace status and outputs per record.
  • ~Throttle calculator now recommends the exact plan you need.
  • !Fixed a rare delay-rounding issue on the seconds time unit.
v1.2.02025-09-11
// The first public release
  • +Pace custom workflow action — batch size, delay, and time unit.
  • +Free plan with 200 daily paces, no credit card.
$
+added ~changed !fixed security
Missing something? Help shape what ships next.
Get Started

Ready to stop blasting
and start pacing?

Install free, add the Pace action to your first workflow, and Pace starts throttling your enrollments automatically. Your integrations will thank you.