​
How Wait Works

Pause the workflow for a specified amount of time before continuing to the next action. This allows you to create timed sequences and give users time to complete actions before follow-up messaging.

​
Configuration

Inputs

​
Wait Value
number
required
The amount of time to wait. Must be a positive number.
​
Wait Unit
enum
required
The time unit for the wait duration: seconds, minutes, hours, days, weeks, or months.

Outputs

​
wait_time
number
required
The number of seconds that the wait was for (calculated from wait_value and wait_unit).
​
wait_end_time
string
required
ISO datetime timestamp of when the wait will end.
​
wait_start_time
string
required
ISO datetime timestamp of when the wait started.

​
Use Cases

Email Sequence Timing 
Wait Value: 1
Wait Unit: days
Purpose: Space out welcome email series appropriately
Follow-up Delays 
Wait Value: 2
Wait Unit: hours
Purpose: Allow time for user to complete action before follow-up
Long-term Nurturing 
Wait Value: 1
Wait Unit: weeks
Purpose: Weekly check-ins for trial users
Immediate Sequences 
Wait Value: 30
Wait Unit: minutes
Purpose: Brief delay for system processing before next action

​
Best Practices

Timing Strategy
  • Choose wait times that align with user behavior patterns
  • Consider time zones for global audiences
  • Test different wait durations to optimize engagement
Sequence Planning
  • Plan entire sequences with appropriate spacing
  • Consider the cumulative impact of multiple waits
  • Align wait times with business processes and support availability
Performance Considerations
  • Longer waits consume system resources for extended periods
  • Monitor active wait states in your workflows
  • Consider using absolute time triggers for very long waits