Schedule Flow
Schedule Flow lets you delay when a flow gets triggered. Instead of firing immediately, you can set a wait time based on a fixed duration, a specific date and time, or a dynamic date pulled from a custom field.
You will find it inside any action block in your Flow Builder. Once added, click on it to open the settings and choose your delay type.
Delay Types
- Duration
Waits for a fixed amount of time before triggering the next flow. For example, wait 30 seconds, 5 minutes, or 2 hours.
- Choose Duration from the Delay Type dropdown
- Set the number and unit (Seconds, Minutes, Hours, or Days)
Set Continue Time Limit
This is an optional toggle inside the Duration delay type. When enabled, the flow will only trigger within a specific time window after the delay has passed.
When you hover over the info icon next to this toggle, you will see:
Message will be sent once the bot user's time is within the selected limits, based on the bot user's timezone.
Once enabled, you can set the following:
- Continue between — Set the time window during which the flow is allowed to run. For example, 08:00 to 22:00.
- Days — Select which days of the week the flow can trigger.
- Timezone — Choose Bot User Timezone to respect each user's local time, or select a fixed timezone.
Tip: This is useful when sending follow-up messages. Set a business hours window so messages never go out in the middle of the night.
- Specified Date and Time
Triggers the flow at an exact date and time you choose. Good for fixed campaign dates or scheduled announcements where the timing is the same for everyone.
- Choose Specified Date and Time from the dropdown
- Pick the exact day and time using the date picker
- Dynamic Date and Time
Instead of a fixed time, this option reads a date from a custom field stored against the user. This means the delay is different for each user based on their own data.
- Choose Dynamic Date and Time from the dropdown
- Select the custom field that holds the date and time value
- Optionally add an Offset to trigger the flow before or after the stored date
This works well for appointment reminders, booking follow-ups, or subscription renewals where every user has their own specific date.