Skip to main content
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

​
Webhook authentication

By default, the webhook URL is the only credential. Anyone who has the URL can call it, so treat it as a secret. For stronger protection, turn on Require API key on the trigger. Every request must then send a company API key (see Authentication) in the Authorization header. Generate a dedicated key for this under Settings > API Keys and set its Scope to Webhooks only:
  • The key must belong to the same company as the automation. A key from another company is rejected.
  • A request with a missing or invalid key gets 401 Unauthorized and does not run the automation.
  • Before you turn the setting on, make sure the system that calls the webhook already sends the header. Otherwise its requests start failing right away.

​
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.