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.
Delay Task Processing
Scenario: A support team doesnβt want to immediately assign newly created tasks. They wait 12 hours to see if more context or similar tasks appear.
βSteps:
βTrigger: Task Added (when a new ticket or task is created).
βDelay For: 12 hours (to collect additional details or related tasks).
βRun Agent Command: Use a task triage agent trained on past tickets to analyze keywords and suggest the best assignee/solution.
βAssign Task: Automatically assign the task to a team member.
Set Up Drip Campaigns
Scenario: A marketing team plans a series of product announcements to be published on different platforms in a staggered fashion.
βSteps:
βSchedule Trigger: Set for the first product announcement.
βCreate Post: Publish the initial announcement on X/Twitter.
βDelay For: Pause for a specific period before the next announcement.
βCreate Post: Publish the second announcement to another platform.
βDelay For: Pause for a specific period before the next announcement.
βCreate Post: Publish the final message, completing the drip campaign.
Follow-up with New Leads
Scenario: A salesperson sends an email to a lead. They want to wait 48 hours before sending a follow-up to avoid appearing too pushy.
βSteps:
βSend Email: Send a personalized email to a lead.
βDelay For: Wait for 48 hours to give the lead time to respond.
βFind Email(s): Search Gmail for replies from the lead.
βBranch:
βIf a reply is found:
βAdd Task: Automatically create a new task in a tracker project.
βAssign Task: Assign the task to a salesperson.
β
If no reply is found:
βSend Email: Send a follow-up email using a template.
β
π 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