Overview
The Delay Until action pauses workflow execution until a specific date and time. The workflow automatically resumes at the scheduled time.
How It Works
Workflow execution pauses at the delay step
Execution resumes automatically at the specified datetime
Workflow context is preserved during the delay
Configuration
Date and Time (Required)
Target datetime to resume execution. Supports multiple formats:
Formats:
YYYY-MM-DD HH:MM- e.g.,2024-12-25 14:30YYYY-MM-DDTHH:MM- ISO 8601 format, e.g.,2024-12-25T14:30YYYY-MM-DD HH:MM:SS- With seconds, e.g.,2024-12-25 14:30:00
Supports Variables:
{booking.date} 09:00- Resume at 9 AM on booking date{addDays(now(), 7)} 10:00- Resume in 7 days at 10 AM
Examples:
2024-12-25 14:30- December 25, 2024 at 2:30 PM{booking.date} 09:00- 9 AM on the booking date{addDays(now(), 1)} 08:00- Tomorrow at 8 AM
Use Cases
Schedule follow-ups for specific dates
Send reminders on booking dates
Schedule tasks for future dates
Create date-specific workflows
Coordinate with external schedules
Examples
1. Booking Day Reminder
Workflow:
Booking Confirmed trigger
Delay Until (
{booking.date} 08:00)Send Notification (day-of reminder)
2. Post-Event Follow-up
Workflow:
Booking Confirmed trigger
Delay Until (
{addDays(booking.date, 1)} 10:00)Send Notification (post-event survey)
3. Scheduled Maintenance
Workflow:
Scheduled Time trigger
Delay Until (
2024-12-31 23:59)Action (maintenance task)
Important Notes
Date must be in the future
Timezone is based on your organization's timezone
Maximum delay may be limited by your plan
Best Practices
Use variables - Reference booking dates, etc.
Verify future dates - Ensure datetime is in the future
Consider timezones - Be aware of timezone conversions
Test thoroughly - Verify delay behavior in test mode