This article explains how to add a wait or delay step to an automation in Remote. Use this step to pause a workflow for a set number of days before the next action runs.
What is the wait or delay step?
The wait or delay step adds a timed pause between actions in an automation. Instead of every step running immediately after the last one, you can insert a gap of 1 to 90 calendar days. The workflow pauses at that point and picks up automatically once the delay period ends.
This is useful when your process needs built-in breathing room. For example, you might want to give a new team member a few days to complete a task before sending a follow-up reminder.
How is this different from scheduling?
Scheduling runs an automation at a fixed, recurring time (for example, every Monday at 9:00 AM). The wait or delay step pauses within a running automation for a specific number of days, then continues. They solve different problems.
Who can use this feature
Only Super Admins and Company Admins (Owners) can create and manage automations.
Employees, contractors, and other team members do not interact with the delay step directly. They experience the result of the delay, such as receiving a reminder email a few days after an initial notification.
How to add a wait or delay step
- Go to Workflows, then select Automations.
- Create a new automation or open an existing one.
- Select a trigger event (for example, "First day of employment").
- select the + button or drag the Wait / Delay step from the sidebar onto the canvas.
- Enter the number of calendar days for the delay. You can set any whole number between 1 and 90.
- Add the next step after the delay (for example, "Send an email" or "Request a document").
- Select Save to publish the automation.
Example: Onboarding follow-up survey
Imagine you want to check in with a new team member a week after they start.
- Trigger: First day of employment.
- Action 1: Send a welcome notification in Slack.
- Wait 7 days.
- Action 2: Send a survey.
What happens during the delay
- The workflow pauses at the wait step. No further actions in that automation run until the delay ends.
- The delay timer starts from the moment the previous step completes.
- After the configured number of calendar days, the workflow resumes and runs the next step automatically.
- If there are multiple wait steps in the same automation, each one pauses and resumes independently in sequence.
Limitations
- Days only: The delay supports whole calendar days (1 to 90). Hours, minutes, and fractional days are not supported.
- No skip-weekends option: The delay counts every calendar day, including weekends and public holidays. A "skip weekends" option is not available in this release.
Frequently asked questions
Can I use more than one wait step in a single automation?
Yes. You can add multiple wait steps to build multi-stage sequences. Each wait step pauses the workflow for the number of days you set before moving to the next action.
Does the delay count weekends and holidays?
Yes. The delay counts every calendar day. There is no option to skip weekends or public holidays at this time.
Can I set a delay in hours instead of days?
No. The wait step only supports whole calendar days between 1 and 90.
Comments
0 comments
Article is closed for comments.