Triggers — Sterodata docs

What starts an automation: the Run button, a button on a table, or a schedule of minutes, hours, days or weeks, or a custom expression.

A trigger is what starts an automation. You choose it under Trigger type in the automation's editor, then save.

Manual

The automation runs when someone starts it:

Run at the top of its editor, or Run now beside it in the list of automations;
a button on a table that runs it. A table's buttons are added from the table's More actions menu, under Custom actions: see Buttons that run an API action.

A button can start an automation whatever its trigger.

Schedule

The automation runs by itself. Pick a Cadence:

Cadence	When it runs
Every 5 minutes, Every 15 minutes, Every 30 minutes	At that interval.
Hourly, Every 6 hours	At that interval.
Daily at 09:00 UTC, Daily at midnight UTC	Once a day, at that time.
Weekly (Mon 09:00 UTC)	Every Monday at 09:00.
Custom expression	Whatever you write in EventBridge expression, below.

Times are in UTC, not your local time: 09:00 UTC is 11:00 or 12:00 in Bucharest, depending on the season.

A custom expression takes one of two forms:

rate(2 hours): every so many minutes, hours or days. Write minute, hour or day for 1, and the plural above 1.
cron(minutes hours day-of-month month day-of-week year): at set times. cron(30 6 ? * 2-6 *) is 06:30 UTC, Monday to Friday. One of the two day fields must be ?.

Sterodata does not check a custom expression when you save. One it cannot use is saved, and the automation never starts by itself. After saving a new expression, check under Recent runs that a run appears when you expect one.

A schedule starts the automation only while it is active: Pause stops it, Activate starts it again. If a run is still going when the next one is due, that turn is skipped.

Webhook

Webhook is listed under Trigger type and shows an address, but nothing reaches an automation through it: a request sent to that address does not start a run. Use Manual or Schedule.