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.
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.
Create a Pace Rule
Open the Pace CRM card on any HubSpot record. Click "New Pace Rule", select the workflow you want to throttle, then set your count (enrollments per batch) and interval (minutes between batches).
Done — Pace Handles the Rest
Turn your rule on. Pace intercepts enrollments to that workflow and releases them in controlled batches according to your rule. Your integrations stay healthy and your sequences feel intentional.
- Active HubSpot account with Admin access
- At least one active workflow to throttle
- No code, API keys, or developer tools needed
- Open the Pace card from any HubSpot record
- Free plan includes 200 daily paces — upgrade anytime
- Rules can be paused and resumed 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:
- 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)
- Each action targets exactly one workflow
- Turning a rule off stops throttling — queued records will continue to drain at your configured rate but no enrollments will go out since the workflow is no longer active
- Your daily pace limit applies across all active rules
- No CRM card setup required — everything is configured in the workflow action
- 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.
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. You can always adjust a rule 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 rule is 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.
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.
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.
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.
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:
- Add the Pace action to your workflow
- Add a Branch immediately after Pace — choose "One property or action output"
- Select "1. Throttle and queue workflow processing" as the action, then choose "Pace Status" as the output field
- Set the value to RATE_LIMITED
- On the RATE_LIMITED branch: end the workflow, send a notification, create a task — whatever makes sense for your use case
- 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.
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 you turn a Pace rule off, the pacing logic continues running at your set rate until the queue is empty — it does not flush immediately. Since the rule is off, each pace processes but no enrollments go out, so the queue drains at your normal rate with no actual workflow activity.
Pace solves a specific problem — uncontrolled enrollment volume. Here are the most common scenarios where Pace makes a real difference.
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.
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.
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 rules in a single day.
Free Forever
- 200 daily paces
- Smart Pacing Controls
- All HubSpot Object Types
- Batch Processing (1–100)
- Flexible Delays
- Email Support
Starter
- 5,000 daily paces
- Smart Pacing Controls
- All HubSpot Object Types
- Batch Processing (1–100)
- Flexible Delays
- Email Support
Professional
- 20,000 daily paces
- Smart Pacing Controls
- All HubSpot Object Types
- Batch Processing (1–100)
- Flexible Delays
- Priority Support
- 40,000 daily paces
- Smart Pacing Controls
- All HubSpot Object Types
- Batch Processing (1–100)
- Flexible Delays
- Dedicated Support
- 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.
Enrollments Aren't Being Released
Check that the Pace rule is toggled on and that you haven't hit your daily pace limit. Also verify the target workflow is still active in HubSpot — Pace cannot release enrollments to a paused workflow.
Enrollments Are All Releasing at Once
This usually means the Pace rule was turned off momentarily — when a rule is disabled, all queued enrollments release immediately. Make sure the rule stays on during your enrollment window.
Running Out of Daily Paces Too Fast
Review your active rules and their count settings. High count values deplete your daily limit quickly. Consider lowering batch sizes, upgrading your plan, or spreading enrollments across multiple days.
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.