Daeda Essentials - Workflow Actions
Every page in this folder is a workflow action you can drop into a HubSpot workflow.
Throttle-first actions
Section titled “Throttle-first actions”| Action | What it does |
|---|---|
| Shared Throttle | Portal-level reusable throttle queues that multiple workflows can share for a combined rate limit |
| Throttle V2 | Per-workflow throttle for capping execution rate at the action level |
| Approval Block | Pauses a workflow until someone manually approves or declines it via a web link |
| Away Block | Pauses a workflow during configured out-of-office hours |
| Meeting Pause | Pauses a workflow when a meeting is on the owner’s calendar |
| Bulk Association | Creates many associations between records in one action |
| Dropdown Select | Programmatically select a value in a multi-checkbox or dropdown property |
| Dropdown Unselect | Programmatically unselect a value in a multi-checkbox or dropdown property |
| OpenRouter | Call any AI model via OpenRouter from inside a workflow |
Pick the action you need from the sidebar - each page covers configuration, inputs, outputs, and example use cases.
Which action should you start with?
Section titled “Which action should you start with?”Start with Shared Throttle when several workflows hit the same downstream limit, such as an SMS provider, enrichment API, custom code action, or external system. Start with Throttle V2 when only one workflow needs paced execution. Use Approval Block, Away Block, and Meeting Pause when the issue is human timing rather than technical rate limits.
Smart Lead & Ticket Routing is separate: use that app for owner assignment, round robin, and out-of-office routing. Use Daeda Essentials for throttling, approvals, and workflow control.
Related
Section titled “Related”- Daeda Essentials on daeda.tech - product page for workflow throttling and control.
- HubSpot workflow throttle alternative - why wait steps are not true rate limits.
- Shared Throttle guide - configure a portal-level queue across workflows.