Delay is an in-built tool in viaSocket that helps you pause your workflows for a specified amount of time before the next actions take place.
This feature is perfect for scheduling tasks on your timeline, such as sending follow-up emails, creating reminders for incomplete tasks, or triggering automated actions at just the right moment. Whether you need to space out notifications or implement timed responses, Delay keeps your workflow organized and in sync with your goals.
Why Do We Need Delay in a Workflow?
Imagine you run an e-commerce store and use a workflow to send a thank-you email after a purchase. However, bombarding your customer with promotional emails immediately after the thank-you note could feel intrusive.
Without Delay:
The customer completes their purchase.
The thank-you email and promotional emails are sent simultaneously.
The customer might feel overwhelmed, leading to email fatigue.
With Delay:
The customer completes their purchase.
The thank-you email is sent instantly to acknowledge the transaction.
A Delay of 2 days is added to the workflow.
The promotional email about complementary products or discounts is sent, arriving at the right moment when the customer is likely to consider another purchase.
This timing improves the customer experience, nurtures the relationship, and increases the chances of a successful upsell or re-engagement.
Delays are similarly useful in scenarios like:
• Scheduling reminders for incomplete tasks.
• Spacing out notifications to prevent interruptions.
• Automating birthday or anniversary greetings at the exact time.
By adding Delay to workflows, you can create more thoughtful, effective, and user-friendly automation.
Minimum and Maximum Time for Delay
Will Delays Impact Execution Time Limit of the Workflow?
No, adding a delay does not affect the total execution time of your workflow in terms of processing capacity. Delays are simply pauses inserted between steps to control when the next action should run. These pauses do not consume additional resources or extend the overall processing duration counted towards your workflow limits.
For example, if your workflow includes a 2-hour delay before sending a follow-up email, those 2 hours are not considered "active" execution time. The system is merely waiting during that period, and the actual execution resumes when the delay ends.
This ensures that delays help you time your tasks effectively without impacting the efficiency or limits of your workflow's processing.
How to get started with Delay
Step 1 : Once logged into viaSocket, navigate to the workflow editor.
Step 2 : In the workflow editor, search for and select your trigger app. Connect your account, configure the trigger step, and test it to ensure it's working properly.
Step 3 : Next, add an action to your workflow, and select the “Delay” feature from the built in tools.
Step 4: Enter the time limit in seconds, minutes, hours, or days by following the format suggested in the field's placeholder.
Step 5 : Define the actions to be executed after the delay, then test and publish the workflow.
How to map data in delay
You can map dynamic values into the delay action by using data from previous steps. If you want to set the delay time based on data from a previous step, you can easily achieve this by mapping the value using a chip.
Can I track the delay times in my workflow logs?
Yes, you can track the delay times in your workflow logs. The logs will include detailed information about the duration of each delay, offering full transparency regarding the time spent in waiting periods.
This allows you to monitor the workflow’s progress, understand any pauses, and ensure everything is running as expected. You can easily review the timeline to see how long each step takes, including delays, and identify any areas that may need optimization for better efficiency.
.png)
.png)
.png)
.png)
.png)
.png)
