> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstwork.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> Events that start an automation — on change, schedule, webhook, API, recollection, and form submission triggers

Triggers define what starts an automation. Each automation has exactly one trigger.

***

## On Change

Fires when a specific field value changes — most commonly when an application moves to a new stage or status. Admins can optionally filter by the previous value, the new value, or a specific field.

## Schedule

Fires on a recurring time-based schedule. Supports daily, weekly, monthly, and yearly frequencies with configurable intervals, specific days, start/end times, and timezones. Admins can also define a filter rule to target only records that match specific criteria, and attach a callback action (email or Slack message) with threshold-based triggers (count or percentage).

## External API

Fires when a candidate or application is created through an external API call. Admins select which fields should be processed when the automation runs.

## Webhook

Fires when an external system sends an HTTP request to a unique webhook URL generated for the automation. Admins configure field mappings between the incoming payload and the platform's data model, along with a lookup strategy:

* **Get or Create** — Find an existing record or create a new one
* **Get Only** — Only match existing records
* **Create Only** — Always create a new record

## Recollection

Fires when a data re-collection event occurs — typically when a candidate re-submits flagged documents or fields.

## Field Submission

Fires when a specific field is submitted — commonly used for signature events (Review & Sign) to trigger post-signature workflows.