Daeda Essentials walkthrough
See the Throttle V2 action in action - controlling workflow execution rate to protect SMS, sequence, and API actions from being overwhelmed.
Secure your high-volume workflows
WHAT'S IN THE BOX
Caps how fast records move through a single workflow, with priority queues for VIPs and batch or one-at-a-time release.
Why HubSpot rate limiting changed the game → SHARED THROTTLEA named queue defined once at the portal level; point any number of workflows at it and the cap applies to combined volume.
How shared throttle queues work in practice → BUSINESS HOURSRestrict releases to working days and respect time off, so workflows don't fire SMS or sequences while your team is on holiday.
Why your throttle should respect time off →WHY THROTTLE
HubSpot workflows release enrollments as fast as the queue can drain them. That's fine for a property update. It's not fine for anything that talks to a human, hits an external API, or sits behind a vendor's rate limit - which is most of the work serious RevOps teams automate.
THROTTLE V2
Drop Throttle V2 into a workflow before the sensitive action and configure two things: how many records to release and how often. Throttle V2 holds the rest of the queue until the next release window opens - the workflow keeps flowing, the vendor stays happy, and nothing gets dropped.
SHARED THROTTLE
When three different workflows all hit the same SMS provider or external API, three separate Throttle V2 actions each hold their own line - and the combined volume blows past the vendor cap anyway. Shared Throttle solves that with a named queue defined once at the portal level, exposed as a dropdown in any workflow.
Built by Jack & Tikita
Daeda Essentials is built by the same small team writing the docs, answering the support threads, and shipping the HubSpot apps behind Daeda.