Flow Basics
Wait
Pause the workflow execution for a period of time before continuing
The Wait node pauses workflow execution for a specified number of seconds before continuing to the next node. This is useful for rate limiting, adding delays between API calls, or creating time-based workflow controls.
When to Use It
- Add delays between API calls to respect rate limits
- Pause before retrying failed operations
- Create time-based workflow controls
- Space out email sends or notifications
- Allow time for external systems to process data
Inputs
| Field | Type | Required | Description |
|---|---|---|---|
| Seconds to Wait | Dynamic-number | Yes | Number of seconds to pause (1-90 seconds max) |
Seconds to Wait
Enter any number between 1 and 90 seconds. The workflow will pause for exactly this duration before proceeding to the next connected node.Output
Returns a simple confirmation message indicating the wait period has completed.Credit Cost
- Cost per run: Free (0 credits)
FAQs
What's the maximum wait time?
What's the maximum wait time?
The maximum wait time is 90 seconds. For longer delays, consider using multiple Wait nodes in sequence or implementing time-based triggers instead.
Does the wait affect parallel workflow branches?
Does the wait affect parallel workflow branches?
No, the Wait node only pauses the specific workflow path it’s placed on. Other parallel branches will continue executing normally.
Can I use dynamic values for the wait time?
Can I use dynamic values for the wait time?
Yes, you can connect the output from previous nodes to dynamically set the wait duration, as long as the value is between 1-90 seconds.
What happens if I enter a value outside the 1-90 range?
What happens if I enter a value outside the 1-90 range?
Values below 1 will be set to 1 second, and values above 90 will be set to 90 seconds. The node will show a validation error if you try to save invalid values.