Skip to main content
View as Markdown

Triggers Overview

A trigger is the single event that starts an automation. Every automation declares exactly one trigger object whose type selects the variant; the remaining properties configure it. Sovrium ships nine types.

app.yaml
automations:
  - name: order-webhook
    trigger:
      type: webhook
      method: POST
    actions:
      - { name: ack, type: webhook, operator: response, props: { status: 202 } }

Trigger Catalog

type Fires when… Key context exposed
webhook An inbound HTTP request hits the automation's endpoint. {{trigger.data.body.*}}, headers, query
cron A cron schedule elapses. scheduled time
record A record is created, updated, or deleted in a watched table. {{trigger.data.record.*}}
auth An authentication event occurs (sign-up, sign-in, …). the auth event + user
form A top-level form is submitted. {{trigger.data.*}} (form values)
manual An admin clicks a button or calls the trigger API. {{trigger.input.*}}
automation-call Another automation invokes this one via the automation/call action. {{trigger.input.*}}, {{trigger.caller}}
automation-failure A watched automation fails. the failed run + error
comment A comment is created on a record. $trigger.comment.*, $trigger.record.*

Webhook Trigger

Moved to Webhook & Cron Triggers.

Cron Trigger

Moved to Webhook & Cron Triggers.

Record Trigger

Moved to Record & Comment Triggers.

Auth Trigger

Moved to Auth & Form Triggers.

Form Trigger

Moved to Auth & Form Triggers.

Manual Trigger

Moved to Manual, Sub-Automation & Failure Triggers.

Automation-Call Trigger

Moved to Manual, Sub-Automation & Failure Triggers.

Automation-Failure Trigger

Moved to Manual, Sub-Automation & Failure Triggers.

Comment Trigger

Moved to Record & Comment Triggers.

Last updated August 11, 2026

This documentation was written with AI, so errors or outdated content are possible. Sovrium is in beta. Contributions and corrections are welcome.

Built with Sovrium