Waits: delay and wait for an event
Wait nodes pause your workflow: Wait (delay) resumes after a fixed duration, and Wait until an event happens resumes when something occurs on the conversation.
Watch this step in the video · Wait time and wait for an event
What they are and when to use them
The Waits section of the node panel holds two nodes that pause a workflow run:
- Wait (delay): resumes the flow after a fixed duration (seconds, minutes, hours, or days).
- Wait until an event happens: resumes when something specific occurs on the conversation or contact, with an optional timeout.
Use them for paced sequences (a 24-hour follow-up), to give the customer time to reply before escalating, or to chain campaigns across several days.
Requirements
- Available on all plans (from Lite), with a monthly quota of workflow runs based on your plan.
- A workflow with a trigger and at least one downstream node to continue to.
Wait (delay)
- In the Nodes tab, open the Waits section and drag Wait onto the canvas.
- In the inspector set the duration and the unit: seconds, minutes, hours, or days.
- Wire the output to the node that should run when the wait ends.
- Click Save.
Short waits continue via a queued job; long waits (days) are persisted: the engine stamps a resume time and a scheduled process picks the run back up when the moment arrives. This is restart-safe: if the worker dies, the run stays in waiting and resumes on its own.
Wait until an event happens
- Drag Wait until an event happens onto the canvas.
- Pick the event type to wait for:
- Contact reply — any inbound message.
- Conversation assigned.
- Conversation closed.
- Lifecycle stage changed.
- Tag added.
- If relevant, set filters (e.g. the tag name, the stage, or the assignee).
- Set the timeout (minutes): if the event hasn't happened by then, the run takes the Timeout branch. A value of 0 = wait forever.
- Wire two outputs: Event (when the event fires) and Timeout.
- Click Save.
Verify
Run a Test and watch the execution timeline: the wait node shows as "waiting" until the time elapses or the event arrives. For long persisted waits, the run sits in a waiting state with a visible resume time.
If it doesn't work
- Flow doesn't continue after Wait: confirm the duration is greater than 0 and that a node is connected to the output; with no next node the wait is skipped.
- The event never arrives: always set a timeout and wire the Timeout branch so runs don't hang forever.
- It resumes too early: check the event filters; a filter that's too broad (e.g. any tag) can match sooner than expected.
Tips
- Use a 24-hour Wait + Send WhatsApp template to re-engage conversations within the 24-hour window.
- Combine Wait until an event happens (Contact reply) with the Timeout branch to escalate to a human agent only when the customer doesn't respond.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.