tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Delay Workflow Step: Pause for a Time or Until a Date

FlowMattic Delay module: a WooCommerce order waits seven days on a Delay For step before a review request email is sent.

A delay workflow step pauses a run and picks it up later, so a follow-up lands three days after a purchase or a reminder arrives at 9:00 in the customer’s own time zone. In FlowMattic, the Delay module does this with two actions: wait for a duration, or wait until a date and time.

Timing is half of good automation. Delay suits review requests, trial reminders, booking reminders, and any process where an immediate action would be too early. The rest of the workflow stays on one canvas, and the waiting run is visible in Task History the whole time.

What is the Delay module?

Delay by FlowMattic is a built-in step in the Flow Controls group, described as “Pause the run for a set time before continuing.” It has two action events:

  • Delay For: “Wait for a certain amount of time before executing the action step.”
  • Delay Until: “Wait to execute the action step until the set date or time.”

Everything before the Delay runs straight away; everything after it waits. Delay sits alongside the other workflow logic modules and works inside Router routes too.

How a delay workflow step works

  1. Add a step where the pause belongs and choose Delay by FlowMattic.
  2. Pick Delay For or Delay Until as the action event.
  3. For Delay For, set the Delay Unit and the Delay Value. For Delay Until, set the Delay Date & Time and the Time Zone.
  4. Add the steps that should run after the wait.
  5. Test the step: it reports the wait it would apply, such as “Execution delayed for 3 days”, without actually pausing.
FlowMattic Delay step Configure tab with the Delay Date & Time field and the Time Zone dropdown.
A Delay Until step that resumes the run at a set date and time, read in the Europe/London time zone.

Behind the scenes, short and long waits are handled differently. A wait of 59 seconds or less happens inside the same run, and the next step follows straight after. A wait of 60 seconds or more is booked in FlowMattic’s own job table: the run is parked, Task History shows it as Waiting, and it resumes at the next step when the job is due. A recovery check also runs every five minutes, so a delayed step whose scheduled job went missing is queued again rather than left waiting for good.

Delay settings

SettingActionWhat it does
Delay UnitDelay ForSeconds, Minutes, Hours, Days or Weeks.
Delay ValueDelay ForHow many units to wait. Whole numbers only; it accepts a dynamic tag, so the wait can come from earlier data.
Delay Date & TimeDelay UntilThe moment to resume, in YYYY-MM-DD HH:mm:ss format, for example 2026-12-10 14:15:30. Accepts a dynamic tag.
Time ZoneDelay UntilThe time zone the date is read in. Defaults to the site time zone from Settings → General; you can pick any region, UTC or a manual offset such as UTC+5.5. Added in 7.3.0.

A date that carries its own offset, such as 2026-12-10T14:15:30+02:00, keeps that offset whatever the Time Zone setting says. If the Delay Until time has already passed when the step runs, the workflow continues immediately instead of waiting. If the date or time zone can’t be read, or the mapped date is empty, the step fails and the run stops there.

Use cases

Ask for a review a week after purchase

A review request sent at checkout is too early. One week later, the customer has used the product.

WooCommerce new order → Delay For (7 Days) → Send Template Email (review request)

Remind a booking the day before, at a local hour

Work out the reminder time from the booking date, then wait until it in the customer’s time zone.

Bookings New Booking → Date/Time Formatter (Add/Subtract Time: minus 1 day) → Delay Until (Time Zone: Europe/London) → Send Email reminder

Nudge trial users before the trial ends

A SaaS product with a 14-day trial reminds new users on day 12, then follows up with a direct message to sales.

WordPress New User → Delay For (12 Days) → Send Email (trial ending) → Slack Send Channel Message to #sales

Give an external system time to catch up

Some APIs confirm a request before the data is ready. A short wait before the lookup avoids reading an empty record.

Webhook (export requested) → Delay For (30 Seconds) → API request (download export) → Google Sheets Add New Row

Send a satisfaction survey after support closes a ticket

Asking for feedback the moment a ticket closes feels automatic. A day later reads as a genuine check-in.

Fluent Support Agent Closes a Ticket → Delay For (1 Day) → Send Email (survey link)

Publish client content at a set launch time

An agency approves a post during the week and wants the announcement out at the client’s launch time, mapped from the request.

Webhook (launch_at field) → Delay Until ({webhook1.launch_at}, Time Zone: America/New_York) → Slack Send Channel Message → Send Email to the client

Let an AI-drafted reply wait for a human window

An AI Agent drafts a reply to an inbound lead, and a short delay gives your team time to cancel the run from Task History if the draft is off.

Form submission → AI Agent (draft reply) → Slack Send Channel Message (draft for review) → Delay For (2 Hours) → Send Email to the lead

Tips and gotchas

  • Long delays need something to wake the site. On a site connected to FlowMattic Cloud, Cloud wakes the site when a wait ends: on the minute on the Free plan, to the second on paid plans. Without Cloud, WordPress cron runs it, and on a site with little traffic WP-Cron only runs on page visits, so a run can resume later than planned. A real server cron job calling wp-cron.php keeps timing tight.
  • Cancel from Task History. A run that is Waiting on a delay can be cancelled from its details in Task History; the steps after the Delay then never run.
  • Switching the workflow off closes waiting runs. If a delay ends while the workflow is off, the waiting run is settled instead of continuing.
  • Whole numbers only. Delay Value is read as a whole number. For 90 minutes, use 90 Minutes rather than 1.5 Hours.
  • Mind the date format. Delay Until expects YYYY-MM-DD HH:mm:ss. Use the Date/Time Formatter to reshape a date from another app before the Delay.
  • Short waits hold the request. A wait under 60 seconds pauses inside the running request, so keep those for brief gaps and use minutes or more for anything longer.

Related features

  • Task History: see Waiting runs and cancel a delay before it ends.
  • Scheduler: start workflows on a timetable instead of pausing one mid-run.
  • Date/Time Formatter: calculate the exact moment for Delay Until.

FAQ

How long can a Delay wait?

Delay For goes up to weeks as its largest unit, with any whole number of units. Delay Until waits for whatever date and time you set. Long waits are booked in FlowMattic’s job table, so nothing is held open in the meantime.

Can I delay until a time in the customer’s time zone?

Yes. Delay Until has a Time Zone setting with any region, UTC or a manual offset. Leave it at the default to use the site time zone.

What happens if the Delay Until time is in the past?

The workflow continues immediately. The step records that the time had already passed and moves on to the next step.

Can I stop a delayed run?

Yes. Open the run in Task History while it shows Waiting and cancel the delay. A cancelled delay stays cancelled, and the remaining steps don’t run.

Delay is part of every FlowMattic plan, with unlimited workflows and runs on your own server. Pick a plan and add the right timing to your next delay workflow step.

More from the blog