Overview
The Delay action pauses an automation for a specified time period (Delay For) or until a specific date and time (Delay Until) before continuing. This lets you precisely schedule actions within your automation workflows.
π‘ Note: Be sure to explore other automation actions & triggers.
Use the Delay Action
Add steps and triggers to build your automation flow.
βClick β Add Step and choose the Delay action.
βInsert the Delay Action directly before the action you want to delay.
β
Configure the Delay action in the right sidebar.
Add more steps and finish the setup.
Delay (Settings)
Connector options give you full control over the Delay action:
π·οΈ Field | π€ Description |
Delay For | Pause the automation for a specific duration of time (seconds, minutes, hours, days, weeks, months) before continuing to the next action. |
Delay Until | Pause the workflow until a specific date and time, which can be sourced dynamically from previous steps. |
Use Cases
Not sure how to use the Delay action? Start with the ideas below.
πͺ Use Case | π Scenario | β© Action Flow |
Delay task processing | A support team delays task assignment to gather more context. | A task is created, and the system pauses for 12 hours to collect additional context. After the delay, the task is triaged by AI to suggest the best assignee or solution. It is then assigned to the right team member. |
Drip campaigns | A marketing team schedules staggered product announcements. | The first product announcement is published. Then, the system pauses for a set period before the next announcement is posted. The cycle repeats until all posts are made, completing the drip campaign. |
New lead follow-up | A salesperson sends an email and waits before sending a follow-up. | A lead is sent a personalized email, and the system pauses for 48 hours. After the delay, the system checks for a response. If no response is received, a follow-up email is sent automatically. |
Automated weekly report | A team automatically sends weekly reports every Monday. | The system triggers every Monday to collect relevant data, waits for the scheduled time, and then sends out a weekly report email to the team. |
Post-Event Feedback | Collect feedback after an event concludes. | After an event ends, the system waits for a set amount of time before sending a feedback request email to the participants. |
Sales reply follow-up | Sales follow up with customers who havenβt responded. | A sales email is sent to a lead, and the system waits for a specific time (48 hours). If no reply is received, the system sends a follow-up email. Otherwise, a task is created for the sales rep to handle the conversation. |
β
π Helpful Links
Download our apps: taskade.com/downloads
Leave feedback: taskade.com/feedback
Changelog: taskade.com/blog/updates
Watch tutorials: youtube.com/taskade
Contact us: taskade.com/contact