Help Center

Automation triggers: what starts an automation

Every automation has one trigger. The trigger decides when the automation runs, and you can change it at any time.

The trigger types

• Manual: runs when you click Run now, or when your own code calls it through the API.
• On record created: runs when a new record is added to the table you pick.
• On record updated: runs when a record in that table is changed.
• On record deleted: runs when a record in that table is removed.
• On a schedule: runs at a recurring time.
• Webhook: runs when another service sends a request to the automation's webhook URL.

Record triggers

Pick the table to watch. The record that caused the run is handed to the steps, so a step can use its fields. For example, an automation triggered by a new order can put the order number in an email subject.

Record triggers watch the table itself. They fire however the record was changed: on a page, by the assistant, by an import or through the API.

Schedules

Choose how often it runs from the presets: every 15 minutes, every 30 minutes, every hour, every 6 hours, every day at midnight, every day at 9 AM, every weekday at 9 AM, every Monday at 9 AM, or on the 1st of every month.

Choose Custom to enter your own cron expression in the 5-field format (minute, hour, day, month, weekday). For example, 0 9 * * 1-5 is every weekday at 9.

Webhook

A webhook trigger gives the automation its own URL. Paste that URL into the service that should start the automation, and it runs every time that service sends a POST request. See Trigger an automation from another service.

Manual

A manual automation runs on demand. Open it and click Run now. An active automation with a Manual or Webhook trigger can also be run from your own code with an API key. See Run an automation from your own code.

Change the trigger

1. Open the automation.
2. Click the Edit button in the header.
3. In Automation settings, pick a different trigger. For a record trigger, choose the table. For a schedule, choose how often.
4. Save.

Avoid loops

An "on record updated" automation that updates records in the same table it watches can trigger itself again. If a step has to write back to that table, ask the assistant to add a condition so the automation only acts on the change you care about, such as a status moving to "Completed".