Wait
Add delays between operations
Overview
The Wait utility pauses flow execution for a specified duration. This is useful for rate limiting API calls, waiting for external processes to complete, or adding delays between operations.
The flow will pause at this node, then continue after the specified time has elapsed.
Configuration
Seconds
The number of seconds to wait. Enter a number or use a template.
Limits
- Minimum: 1 second
- Maximum: 1800 seconds (30 minutes)
- Default: 5 seconds
Dynamic Values
Use templates for dynamic wait times:
{{#1.data.delaySeconds}}Output
Wait outputs timing information about the delay:
Output fields:
waitedSeconds- Configured wait time in secondsactualDuration- Actual execution time in secondscompletedAt- ISO timestamp when the wait completed
Examples
Example 1: API Rate Limiting
Add delay between API calls to avoid rate limits:
[Iterator] ──▶ [HTTP Request] ──▶ [Wait: 1s] ──▶ [Next Request]
│ │
▼ ▼
Item 1 1 second delay
Item 2 before next item
...With 60 items, this ensures max 60 requests per minute.
Example 2: Wait for Processing
Wait for an external service to complete processing:
[Submit Job] ──▶ [Wait: 30s] ──▶ [Check Status] ──▶ [IF: Complete]
│ │
▼ No ────┴──── Yes
Wait for job [Wait + Retry] [Get Results]Example 3: Staggered Notifications
Send notifications with delays to avoid overwhelming recipients:
5sEach notification is sent 5 seconds apart.
Tips
Tip: Use Wait inside iterators to add delays between each item being processed, not just at the end.
Tip: For dynamic delays, use a template in the duration field:{{#1.data.delaySeconds}}s
Note: Long waits (hours) keep executions active. Consider using scheduled triggers instead for very long delays.
Billing: Wait time counts toward execution time. Use only when necessary.