Schedules and triggers

A flow starts when its file says: on a cron with a timezone, when a webhook arrives, when an email lands in its inbox, when another flow finishes, when a file appears, when a page changes.

Read the docs Get early access

flows/rankings.md

trigger: schedule
schedule: "0 5 * * 3"
timezone: Australia/Sydney

next run in …

schedulewebhookemailflowstoragewatch

runs started 0

A clock, a webhook, an inbox, another flow, a file, a URL. Nine ways in.

Cron with a timezone, in one line of the flow

Nine kinds of trigger, including email and webhooks

Chain flows: one finishing starts the next

Overlap policy per flow: skip, queue or run alongside

Runs in the cloud Secure by construction Any model, your key Approval gates Budgets, not timeouts Git is the deploy Memory that survives Every run on the record Unlimited seats