Skip to main content

Triggers

The trigger is the first block of every automation (the START block). It defines when the automation runs. Select one of three modes at the top of the trigger panel: Record event, Schedule, or On demand.

Open any automation in Automation from the top navigation, then select the trigger block to configure it. Until its required fields are set, the block shows a needs config badge.

Record event​

Runs when a record is created, updated, or deleted in a collection.

FieldRequiredDescription
EventYesThe database operation that fires the trigger: Created, Updated, or Deleted.
Execution PhaseYesBefore or After the database operation (see below).
TableYesThe collection whose records fire the trigger.
AliasYesA reference name for the trigger record, used downstream as {{alias.field}}.

Execution phase​

  • Before — Runs before the record is saved. Use it to validate or transform data, or to prevent the operation.
  • After — Runs after the record is saved. The record exists with its final values.
tip

Use Before for validation and transforms; use After for notifications and integrations.

Auth table (optional)​

Access data about the authenticated user who performed the operation.

FieldDescription
Auth TableThe auth collection to read the acting user from. Defaults to No auth table.
Auth AliasA reference name for the user record (for example, authUser).

Filter conditions (optional)​

Add conditions so the trigger fires only for matching records. Click Add condition to add a row, and remove a row with its ×. Each row is a field, an operator, and (for most operators) a value. All rows are combined with AND — the trigger fires only when every condition is met.

Operators:

OperatorNotes
Has changedFires only when the field's value changes — pair it with the Updated event. Takes no value.
Equals / Not equal toMatch or exclude a value.
Is any of / Is none ofMatch against any of several values.
Is empty / Is not emptyTake no value.

The value input matches the field type — a choice field shows a dropdown, for example. Insert a {{alias.field}} token with the + picker.

Schedule​

Runs on a recurring interval or once at a fixed time. Useful for maintenance jobs and time-based reports.

FieldRequiredDescription
IntervalYesHow often to run: Minutes, Hours, Days, Weeks, Months, or One time.
EveryYesThe interval count (for example, 1 with Hours runs every hour).
Start dateYesThe date of the first run.
Start timeYesThe time of the first run. The time picker uses 5-minute steps.
note

Schedule triggers have no trigger record or alias — no {{alias.field}} data is available from the trigger itself. Use a Record block to query the data you need.

On demand​

Runs when called from another automation, a cron job, or a queue. It is not tied to a record or schedule.

FieldDescription
AsyncTurn on to run without blocking the caller.
Input ParametersThe arguments the automation accepts. Click Add parameter to add one.

Input parameters​

Each parameter has:

FieldDescription
NameThe parameter name. Must be camelCase (for example, applicationId).
TypeThe value type: Void, Boolean, String, Number, Object, or Array.
ArrayTurn on Multiple values to accept a list of this type.
Object SourceShown when Type is Object. Defines the shape from a Collection or a JSON Object.
Default ValueOptional value used when the caller omits the parameter.

Response type​

Every trigger mode ends with a Response Type that defines what the automation returns: Void (default), Boolean, String, Number, Object, or Array. For Object or Array, pick an Object Source — a Collection or a JSON Object — to define the shape.

Examples​

Trigger on new approved users

Record event: Created — Table: Users (alias: user)
  Filter: status Equals "approved"
Action: Send Email → To: {{user.email}}

Nightly cleanup

Schedule: Every 1 Days at 02:00
Record: Find All from Sessions (alias: sessions) where expiresAt < now
Action: Mutation (Delete) Sessions where id in {{sessions.ids}}