Wait

Pause a run for a fixed time, until a specific date, or until a webhook or form submission resumes it.

At a glanceVerified in app · Oct 29, 2026

Use it to: Pause an automation mid-run without holding an execution slot
Find it: Tools → Flow → Wait (shortcut f then d)
Cost: Free (0 Step credits while waiting)
Limits: Up to 13 days (1,123,200 seconds) per wait
Output: {{ N.result }} (or {{ N.formData.<field> }} on form resume; Resumed / Expired routes)
Instead: Scheduler Trigger (for starting on a recurring clock) or Human Review (for reviewer sign-off)

Find it under Flow in the Tools panel, or place it with the f then d shortcut.

A waiting run is not running. Glow puts the run down and picks it up when the wait is over.

Setting it up

The first field is Wait Mode, and it changes every field below it. The four modes are:

Wait Mode	Continues when
For a time interval	The amount of time you set has passed
Until a specific date and time	The clock reaches the date and time you set
On webhook call	Another system calls this run’s resume address
On form submitted	Somebody fills in a form and submits it

The default is For a time interval.

Time Interval

Set Amount (defaults to 5) and Unit (Seconds, Minutes, Hours, or Days).

Use this mode to space out calls to an external service or give a system a moment before reading back a record you just wrote.

Until Date and Time

Set Resume at (such as 2026-01-01 09:00 or {{ 2.renewalDate }}) and Timezone:

Default timezone: Saves the Workspace timezone, or the creator’s personal timezone, then UTC. Daylight saving is applied for the target date.
Explicit offsets: Values ending in Z or +02:00 are treated as absolute instants, ignoring the Timezone field.
Past timestamps: If the target moment has already passed when the Step runs, execution continues immediately without failing.

On Webhook Call

When the Step runs, Glow pauses the run and generates a single-use {{ 4.resumeUrl }} for that execution. Select the paused Step and click Copy resume URL under Webhook resume URL in the App drawer (or inspect the pending output in Executions).

Anything the caller POSTs to that URL arrives in formData (for example, {"orderId": "A-91", "status": "shipped"} exposes {{ 4.formData.orderId }} and {{ 4.formData.status }}). Calling the URL a second time after the run resumes does nothing.

Do not place the step that delivers resumeUrl or formUrl after Wait. Downstream steps do not run until the wait finishes. Test the run once (using test accounts) and copy the generated URL from Executions or the App drawer.

On Form Submitted

Pauses the run until someone submits a hosted form at formUrl. Both webhook and form modes require a Live published automation to resume.

Field	What it does
Form Title	Heading shown above the form
Form Description	Short explanation shown under the heading
Form Fields	At least one field (Field name, Label, Type, Required, optional Placeholder, Help text, and comma-separated Choices)

Supported field types: short text, long text, number, date, dropdown, multi-select, checkbox, radio, and file. Submitted answers arrive under {{ 4.formData.<fieldName> }} (such as {{ 4.formData.reason }}).

Resumed and Expired

The two waiting modes (On webhook call and On form submitted) give the step two outputs under Branches: Resumed and Expired.

Wired branches: Connect Resumed to the normal path and Expired to a timeout path (such as a chaser email).
Unwired branches: Leaving Branches empty routes resumed runs down the single normal output and expired runs to the Step’s error path.
Timeout (seconds): Sets the deadline. Leave it blank or 0 to wait indefinitely (up to the 13-day ceiling), where only Resumed can fire.

What it passes on

What the step publishes depends on its mode.

For a time interval and Until a specific date and time, the step publishes one value:

Reference	Contains
`{{ N.result }}`	A sentence confirming the wait, e.g. “Next steps will be executed after 2 days”

The two timed modes wait and then carry on, so there is nothing else worth passing down. If a later step needs the moment the run resumed, use {{ $now }} there rather than reading it back off this step.

On webhook call and On form submitted, while the run is paused:


{
  "status": "pending",
  "waitMode": "form",
  "resumeUrl": "https://…",
  "formUrl": "https://…",
  "expiresAt": "2026-08-10T09:00:00.000Z"
}

formUrl is the page a person opens, and appears in form mode only. expiresAt is null when there is no timeout.

Once the wait resumes, the step’s own result carries what came back:

Reference	Contains
`{{ N.formData.<name> }}`	What was submitted, or what the caller sent
`{{ N.decision }}`	`resumed` or `expired`
`{{ N.answeredAt }}`	When the answer arrived

Steps before the Wait are untouched by it. Anything later steps need from them is read as usual.

Limits

A timeout or timed wait runs to a maximum of 13 days (1,123,200 seconds). For longer delays or recurring daily jobs, end the first automation and start a second one on a Scheduler Trigger.

Examples to copy

Stay under a rate limit

Put a Wait of Amount 2, Unit Seconds as the last step of a sequential Repeater loop body before connecting back into Repeater.

Continue on the renewal date

Set Wait Mode to Until a specific date and time and Resume at to {{ 1.renewalDate }}. The run resumes on the date carried in the trigger payload.

Wait for a supplier webhook

Set Wait Mode to On webhook call and Timeout to 172800 (two days). Wire Resumed to the fulfilment Steps and Expired to a chaser email, then copy resumeUrl from the waiting run and register it with the supplier.

Ask for a missing detail

Set Wait Mode to On form submitted and add a short text field named poNumber. Copy the hosted form link from the App drawer once waiting; after submission, downstream Steps read {{ 4.formData.poNumber }}.

Because Glow is multiplayer, a teammate watching a running automation sees when a Wait step started and when it is due to resume.

Verify it works

Run: Set Wait Mode to For a set amount of time (5 seconds) and click Run
You should see: The Step enters Waiting for 5 seconds, then transitions to Completed and runs the next Step.

What’s Next?

Run an automation on a recurring clock instead of pausing mid-run with the Scheduler Trigger.
Ask a named person for a decision, with buttons and branches of your own, using Human Review.
See execution ceilings in System Limits & Quotas.