Skip to main content

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

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

Outputs

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

Use Cases

Email Sequence Timing
Follow-up Delays
Long-term Nurturing
Immediate Sequences

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