Wait for the event that matters
Workflows can pause until a specific event happens, so the next step follows real activity instead of a fixed delay.
A closer look
What changed
A Wait for event node can pause one branch of a Workflow until a selected record event occurs. The Workflow follows the Then path when the event matches or the Timeout path when the configured wait expires. Optional conditions can decide which arriving events count.
Why it matters
Follow up work can respond to what actually happened instead of relying only on a fixed delay, while the timeout path provides a clear fallback when the expected event never arrives.
How to use it
- 1Add Wait for event at the point where the Workflow should pause.
- 2Select one supported event and, if needed, define record conditions that must be true when it arrives.
- 3Set a timeout of up to 30 days.
- 4Connect both the Then and Timeout paths, then verify the Workflow before publishing.
Example
After sending an onboarding task, wait for Task completed. Continue the successful path when it is completed, or notify a manager when the timeout is reached.
Availability
The production implementation is present for eligible Workflows accounts. Confirm availability with Customer Success before relying on it for a critical process.
Ask Customer SuccessGood to know
- The event picker currently supports one event per Wait node.
- Events created by the same Workflow are ignored by default. An advanced option can include them.
- The editor does not yet show a parked run as Waiting in a dedicated execution view.
Step by step guides
Wait for event
Pause a Workflow until the selected event occurs, then continue with the latest context.
More responsive automation
Build follow up steps around what people actually do instead of relying only on a preset amount of time.
