Flows let you automate how you interact with customers. Use them to reactivate inactive shoppers, send birthday and anniversary greetings, deliver digests, and much more.Scheduled flows run at a specific time on a recurring cadence. For example, every day at 10:00 AM, every weekday at 3:00 PM, or at 8:00 PM on the last day of every month.To create a scheduled flow, open the start block and choose By schedule. Then set when and how often the flow should run, and which customers should enter it.
To trigger a flow in response to customer actions instead, see the article on event-based flows.
Below are the available scheduling options, plus the key details to keep in mind when working with periodic flows.
Runs on specific days every N weeks. Pick the days of the week, the time, and the repeat frequency.Example: The flow runs every second Friday at 3:00 PM.
After you turn the flow on, the Schedule block waits until the time you set, then runs for the customers who match its conditions at that moment.Example: You turn the flow on at 5:00 PM.
It will run every day at 10:00 AM for the customers who are in the segment at that time.
You can set a start date and an end date for the flow. This is useful for time-limited campaigns and helps you automate when they begin and end.To do this, open the flow settings and set the dates.Example: The flow only runs during March 2023.
A customer can match a flow’s conditions many times.For example, a reactivation flow checks for no orders in the last 30 days and sends a campaign. Without a frequency cap, the flow will run for that customer every day until they make a purchase.Another example: a customer edits their birth date in their profile. Without a safeguard, the birthday flow will issue bonuses again.You can prevent this by capping how often the flow runs per customer.Example: The birthday flow runs only once per calendar year for a given customer, even if they update their data.
Flow schedules use the project’s time zone. If your team works from different locations, your local time may not match the project’s time.You can find the project time zone under Settings → System → Platform Parameters.
Flows have throughput limits per unit of time. Running a flow against half of your customer base will take several hours.Heavy filters can also add processing time. If a filter can’t be calculated within four hours, the flow stops and an alert is opened.
Plan large scheduled flows with throughput in mind. Complex filters and big audience sizes can push processing into multiple hours, and filters that exceed four hours will halt the flow.