Throttle V2
Overview
What it does: Controls the rate at which workflows execute by creating intelligent queues that release batches of workflows at specified intervals.
When to use it: When you need to prevent overwhelming external systems, manage API rate limits, or control the timing of bulk operations like email sends or data updates.
Business value: Protects your integrations from rate limiting, ensures consistent performance, and allows for sophisticated scheduling of workflow executions across different days and times.
Quick Setup
Prerequisites
Basic Configuration
- Add the Throttle V2 action to your workflow
- Set the minimum time interval between batch releases
- Configure how many workflows to release per batch
- Test with a small number of records first
Input Fields
Required Fields
Number of Workflows to Release (Card)
- Type: Number
- Description: How many workflows are released from the queue each time the throttle interval completes
- Example:
5 (releases 5 workflows every interval)
- Notes: Higher numbers process faster but may overwhelm downstream systems
Time Unit
- Type: Dropdown
- Description: The unit of time for your throttle interval
- Options: Seconds, Minutes, Hours, Days
- Example:
Minutes (combined with time value for "every 5 minutes")
Minimum Time Between Workflows
- Type: Number
- Description: The interval duration combined with the time unit above
- Example:
30 (with "Minutes" = every 30 minutes)
- Notes: First execution happens AFTER this interval, not immediately
Optional Fields
Execution Priority
- Type: Text/Property
- Description: Controls execution order within the queue using HubSpot priority values or custom numbers
- Default: No priority (first-in-first-out)
- Example:
{{task.hs_task_priority}} or 7 (0-9 scale, higher = first)
- Notes: Supports HubSpot priorities (HIGH, MEDIUM, LOW, NONE) or numeric values
Initial Execution DateTime
- Type: Date/Time
- Description: Sets when the first batch should be released (must be in the future)
- Example:
2024-12-15 09:00:00
- Notes: Only updates if no workflows are currently waiting in the queue
- Important: If you set a release time of 1 day, records will release at the same time every day - either at this initial datetime OR at the time the first record hit the server (if no datetime was provided)
Execution Day Selection
- Type: Checkboxes
- Description: Restricts throttle execution to specific days of the week
- Options: Monday through Sunday (multiple selection)
- Example: Check Monday, Tuesday, Wednesday, Thursday, Friday for business days only
- Notes: If no days selected, throttle works on all days
Common Use Cases
Use Case 1: Email Campaign Rate Limiting
Scenario: Sending personalized emails to 1000+ contacts without triggering spam filters
Setup:
- Card:
50
- Unit:
Minutes
- Time:
15
- Day Select: Monday-Friday only
Result: Sends 50 emails every 15 minutes, only on business days (200 emails/hour max)
Use Case 2: API Integration Protection
Scenario: Syncing contact data to external CRM with 100 requests/hour limit
Setup:
- Card:
10
- Unit:
Minutes
- Time:
6
- Priority:
{{contact.lifecycle_stage}} (prioritize qualified leads)
Result: Makes 10 API calls every 6 minutes (100/hour), processing qualified leads first
Use Case 3: Scheduled Data Processing
Scenario: Daily batch processing of deals that need complex calculations
Setup:
- Card:
25
- Unit:
Hours
- Time:
2
- Initial DateTime:
2024-12-15 02:00:00
- Day Select: Monday-Friday
Result: Processes 25 deals every 2 hours starting at 2 AM, business days only
How It Works
- Workflow Execution: When a record enters the throttle action, it's added to a queue
- Queue Processing: The system processes the queue at your specified intervals
- Batch Release: The configured number of workflows are released each interval
- Priority Ordering: Higher priority items are processed first within each batch
- Day Filtering: Execution only occurs on selected days (if configured)
- Continuation: Released workflows continue to the next action in your workflow
Pausing behavior
If your workflow is turned off - the Throttle V2 action will pause. It will retain all it's current records until the workflow is turned back on, or until the records expire (in 1 year).
Last updated: November 23, 2025