Daeda Throttle
Control how quickly records reach your API calls, messages and other workflow actions. Share one rate cap across workflows, and prioritise the records that matter most.
150 workflow-action executions every month on the free plan.
On HubSpot Marketplace · 100+ installs
One example, from start to finish
Your renewal, onboarding and campaign workflows all send requests to the same provider. Separate limits can still add up to more traffic than the provider allows.
All three workflows now draw from one allowance. Records wait in the shared queue until they can continue.
Create a named Shared Throttle queue for that provider.
Choose a release allowance with room for other traffic. If each record makes one request, a limit of 100 requests per 10 minutes might use 80 releases per 10 minutes.
Add Shared Throttle immediately before the provider action in each workflow, and select the same queue.
Enrol a small test batch and check the combined release rate in the queue view.
Control 1 of 3
A list import or busy campaign can put thousands of records into a workflow at once. Place Throttle V2 before the sensitive action and choose how many records can continue in each release window.
Read the rate-limiting guideControl 2 of 3
When workflows call the same provider, they need to share its allowance too. Define a Shared Throttle queue once and select it in each workflow, so the cap applies to their combined volume.
Explore shared queuesControl 3 of 3
Use a record property to prioritise urgent work within the queue. Add business-day controls when releases should wait for working days, rather than sending human-facing work over a weekend.
Explore the queue controlsA clear fit, with clear boundaries
Daeda Throttle adds a queue before the action you want to pace. It works within your existing workflow, so you can start with one bottleneck.
Use it when you need to pace a downstream action or share an allowance across workflows. If a native HubSpot rate control already covers your action and scope, that may be enough.
A release means a record continues. It does not necessarily mean one API request. Count the requests each record makes, leave headroom for other traffic, and keep the receiving system's retry handling. Calls outside these queues are not limited by Daeda.
“The workflow queue is amazing - my API limit issues are gone.”
Pricing
Choose a monthly execution allowance. The workflow controls stay consistent as your volume increases.
For testing and very low-volume workflows
150 executions every month
Explore the workflow actions and prove the setup in a live HubSpot portal.
For small teams and occasional high-volume jobs
10,000 executions every month
Run recurring workflow controls without worrying about a small test allowance.
For growing RevOps and automation teams
50,000 executions every month
Give active RevOps teams room for regular queues and workflow safeguards.
For large and high-volume HubSpot portals
Unlimited executions
Remove monthly execution limits for high-volume workflow environments.
Monthly usage is measured across Daeda Throttle workflow-action executions in the connected portal.
Daeda Throttle
Install the free plan, add a throttle before one sensitive action, and test the release rate before rolling it out further.
