Triggers

The six ways a flow can start: a record change, a schedule in UTC, a manual Run, a calendar event, a People event or a webhook.

Every flow has exactly one trigger. It is the block the flow starts from. You cannot connect anything into a trigger.

Overview

Trigger Starts when Needs
Record event A record of a chosen type is created, updated or deleted. A record type
Schedule The clock matches a cron schedule. Times are UTC. A cron expression
Manual Someone presses Run. Nothing
Calendar event A calendar event is created, changed, cancelled, or is about to start. Optional: a calendar
People event Leave is requested, approved or rejected, or someone joins or leaves. The People app
Webhook Another tool sends data to the flow's own web address. Nothing — the address is made when you save

A flow that is Off never starts from a trigger. It still starts when you press Run.

Record event

Runs after a record is saved.

Setting Options
Object type Pick a record type. It is shown as "Label (key)".
Event Created, Updated or Deleted. Default Created.
Only when these fields change Shown for Updated. Pick up to 10 fields; empty means every update. With one field you can also set Changed from and Changed to. See Run a flow when a field changes.

What the flow can use from this trigger (all in the Insert value menu under Trigger):

  • Record id and Event.
  • Record · for every field of the record type.
  • On Updated: Changed fields and Before · , the value before the update.

For a Deleted event only the record id and event are available, because the record itself is gone. For created and updated events the record's values are read with the permissions of the person the flow runs as. See Who a flow runs as.

Schedule

Setting Notes
Cron (UTC) Standard 5-field cron: minute, hour, day of month, month, day of week. Example: 0 9 * * *. Times are UTC, not your local time.
Preset Fills the cron for you.

Schedule trigger settings with a cron field and presets

Presets:

Preset Cron
Every 15 minutes */15 * * * *
Hourly 0 * * * *
Daily at 09:00 UTC 0 9 * * *
Weekly (Mon 09:00 UTC) 0 9 * * 1
Monthly (1st 00:00 UTC) 0 0 1 * *

A new Schedule block starts with 0 9 * * *. The flow can use Scheduled time from the Insert value menu. An invalid cron is refused when you save an enabled flow. The next five scheduled runs of enabled flows show on the Overview under Coming up.

Tip: India Standard Time is UTC+5:30. For 09:00 IST, use 30 3 * * *.

Manual

Nothing to configure. The flow runs when you press Run in the builder, or choose Run now from the flow's menu in the list. You need the Can run level (or higher) of the Automations app. The canvas summary reads "on demand".

Calendar event

Setting Options
Calendar Any calendar I can see, or one calendar by name. Calendars that only mirror records are not listed.
When an event Is about to start, Is created, Is changed, Is cancelled. Default Is about to start.
Minutes before it starts Only for Is about to start. A number from 0 to 10080. 0 means at the start. Default 15. Fires once for each occurrence of a repeating event.

What the flow can use (under Trigger): Occurrence start, and Event · id, title, start, end, location, description, calendar key, attendees (list) and linked record id.

The event is read with the permissions of the person the flow runs as. If they cannot read that event, the flow does not run for it. See Calendar.

People event

Setting Options
When Leave is requested, Leave is approved, Leave is rejected, Someone joins or Someone leaves. Default Leave is approved.

The flow can use the employee (code, name, email, phone, designation, department, manager, status, joining and exit dates) and, for leave events, the leave request (type, dates, days, status, reason). It only runs for people the flow's owner can see in People: themselves, their reporting line, or everyone with HR access. Joins and exits dated more than 30 days back — for example from importing old staff — do not start it.

Webhook

Runs when another tool — a payment provider, your online store, a form on another website — sends data to the flow's own web address.

  1. Add a Webhook trigger and save the flow. The Webhook URL appears in the trigger's settings.
  2. Click Copy URL and paste it into the other tool's webhook settings. It must send a POST, usually with a JSON body.
  3. Each delivery starts a run straight away. Past deliveries appear under Runs.
Setting Notes
Webhook URL The address to send to. Anyone who has it can run the flow, so share it only with the sending tool.
New URL Makes a new address when you next save. The old one stops working. Use it if the address has leaked.
Signature header (optional) If the sender signs each delivery, type the name of the header it puts the signature in. Deliveries with a missing or wrong signature are refused.
Signature encoding Hex or Base64 — check the sender's documentation.
Signing secret The secret the sender gave you. It is stored sealed and is never shown again; type a new one to replace it, or tick Remove the signing secret.

What the flow can use (under Trigger in the Insert value menu):

  • Body — add .field for one value, for example {{trigger.body.amount}}.
  • Header — add .name in lower case, for example {{trigger.headers.x-event-type}}.
  • Query string — add .key.
  • Method.

Note: a sender may deliver the same event twice. Build the flow so that running it twice does no harm — for example, look the record up before creating it.

A flow that is Off does not accept deliveries. Each address takes up to 120 deliveries a minute.

Work queue event

Starts when something happens to an item in a work queue: an item is added, moves to a stage, sits in a stage too long, changes priority, tags or assignee, is picked up or let go, gets a comment, or is escalated. For a simple when/then rule you do not need to build this by hand — use the queue's Automations view, which saves an ordinary flow you can open here. See Automate a work queue.

Get told when a run fails

Every trigger has Alert the flow's owner when a run fails, on by default. The owner (the person the flow runs as) gets an inbox notification and an email naming the flow, the block that failed and the error. Add other people under Also alert. You get at most one alert per flow per hour; the next one says how many more failures there were.