Choose a trigger

In this section you will learn about triggers

A trigger defines when a function runs automatically. In the Workflows area, choose Add Automation to start with a trigger, or use Add trigger for an existing function.

Function and automation triggers

Trigger	Starts work
At regular intervals	Repeatedly at a configured interval
Based on a schedule	According to a configured schedule
One-time run	For a single configured execution
When record created	When a new record is created
When record updated	When a record is updated
When record deleted	When a record is deleted

Add Automation menu with interval, schedule, one-time, and record-event triggers

Open Workflows → Add Automation to choose a trigger type.

Follow Functions and automations for screenshots of both menus and the setup sequence. Configure the timing or record source after choosing a type.

Component actions

An app user can also start a workflow from a button or list action. Open the component's Actions configuration and choose Run Workflow. Bind the selected record ID or form values as inputs.

See Run from a button or list action. Component success/error callbacks are another entry point; see Run actions after component success or failure.

External HTTP events

The separately documented webhook setup covers incoming HTTP events. A webhook option is not shown among the six choices in the supplied Add trigger and Add Automation menus.

Check the input and result

Identify the values the function needs, inspect the inputs supplied by the trigger, and map the required fields. A record event and an app's selected row may expose different data.

Test both the function and its actual trigger. For update events, check whether the function's writes can cause another event. For deletion events, inspect the payload rather than assuming the deleted record remains queryable.

See Pass inputs into a workflow and Handle failures and prevent duplicate processing.

Record-event scope

In record-trigger setup, choose the resource and collection. The inspected Jet Tables collection selector explicitly says collections (changes from Jet only). Do not assume that a direct write to an external database will start this automation.

Test creation, updates, and deletion separately using a disposable record changed through Jet. Inspect the event values before mapping them; the available fields and delivery behavior must be verified for your configured trigger.