Set Smarter Workflow Pauses With the Redesigned Wait Action
The Wait action in ESC Hub workflows has been completely rebuilt. What was previously a basic delay step is now a fully redesigned tool with recurring schedules, dynamic durations, and an intent-based setup that makes it far easier to configure exactly the pause you need.
What's changed
Intent-based card selection The old dropdown has been replaced with a card selection screen. Instead of hunting through nested dropdowns, you now pick your intent first - for example "Wait for a contact reply" - then configure from there.
Recurring wait schedules You can now set up recurring waits with weekly, monthly, or yearly frequency. Weekly supports specific days and times, monthly supports options like every first Sunday or the 15th, and yearly supports renewals, holidays, and annual check-ins.
Wait for a specific date - single step Previously this required two separate actions. Now it's one step - pick a fixed date or pull from a custom field directly inside the Wait action.
Seconds as a wait unit Time delay now supports seconds, enabling rapid-fire sequences with two or three-second pauses between actions.
Dynamic wait duration Wait durations can now be set dynamically using the custom value picker - pulling the duration from a custom field, contact field, or any supported variable instead of hardcoding a value.
Grouped wait types Related wait types are now grouped under single cards to reduce clutter. For example, "Wait for a contact action" now includes trigger link clicks and email events in one place.
Wait AI A new CTA at the top of the Wait action lets you describe your desired wait behaviour in natural language. The AI Builder generates a configured Wait action card that can be adjusted directly or refined through conversation.








Why it matters
The Wait action was one of the most-used steps in workflows and one of the most confusing to configure. The redesign addresses both - clearer setup, more options, and less chance of accidentally building a timing issue into your automation.

