Triggers

A trigger defines when an automation starts. Event triggers respond to changes, scheduled triggers run at set times, and conditional triggers respond to record-state transitions.

Event Triggers

Event triggers run after a specific record event or field change.

Record Events

• Record created: Runs when a record is created. A form submission that creates a record also starts this trigger.
• New comment: Runs when a comment is added. You can filter by list, commenter, or mentioned people and groups.
• Record moved between lists: Runs when a record changes lists. Use From list and To list to limit either side of the move. Each filter accepts multiple lists. Leave a filter empty to match any list.
• Record marked complete: Runs when a record becomes complete.
• Record marked incomplete: Runs when a completed record becomes incomplete.
• Record archived: Runs when a record is archived.
• Record unarchived: Runs when a record is restored from the archive.
• Record copied/moved from another workspace: Runs in the receiving workspace after a record arrives from another workspace. The move or copy can come from a person or an automation.
• Record is added to another workspace: Runs when a record is added to another workspace. This trigger requires Pro or Enterprise.

Field Changes

• Assignee added: Runs when an assignee is added. You can limit the trigger to selected assignees.
• Assignee removed: Runs when an assignee is removed. You can limit the trigger to selected assignees.
• Date has changed: Runs when the default due date or a selected custom date field is set or changed.
• Date is removed: Runs when the default due date or a selected custom date field is cleared.
• Date has expired: Runs relative to the default due date or a selected custom date field. Set the trigger before, after, or at expiration. You can restrict it to incomplete records.
• Tag added: Runs when a tag is added. You can limit the trigger to selected tags.
• Tag removed: Runs when a tag is removed. You can limit the trigger to selected tags.
• All checklist items marked as complete: Runs when every checklist item on a record is complete.
• Checklist item marked incomplete: Runs when a completed checklist item becomes incomplete.
• Custom field value is set: Runs when a checkbox, single-select, multiple-select, or assignee field receives a value. Select fields can be limited to specified options.
• Custom field value is removed: Runs when a value is removed from one of the supported custom fields.
• Color added: Runs when a color is added. You can limit the trigger to selected colors.
• Color removed: Runs when a color is removed. You can limit the trigger to selected colors.
• Button clicked: Runs when a person selects the configured button custom field on a record.

GitHub

GitHub triggers appear only when the workspace has a linked repository. See GitHub integration to connect one. Each trigger accepts an optional branch filter that matches against the branch the event targets.

• Branch created: Runs when a branch that references a record is created.
• Pull request opened: Runs when a linked pull request is opened.
• Pull request marked as draft: Runs when a linked pull request is converted to a draft.
• Review requested: Runs when a review is requested on a linked pull request.
• Pull request approved: Runs when a linked pull request is approved.
• Changes requested: Runs when a reviewer requests changes on a linked pull request.
• Pull request merged: Runs when a linked pull request is merged.
• Pull request closed: Runs when a linked pull request is closed without merging.
• Pull request reverted: Runs when a merged pull request is reverted.
• Checks passed: Runs when CI checks pass on a linked pull request.
• Checks failed: Runs when CI checks fail on a linked pull request.
• Commit pushed to default branch: Runs when a commit that references a record is pushed to the repository’s default branch.

Scheduled Triggers

• On schedule: Runs daily, weekly, monthly, or yearly at the configured time and time zone. Blue applies the actions to records that match the filter when the schedule runs.

Scheduled automations require Pro or Enterprise.

Conditional Triggers

• When conditions met: Runs when a record starts or stops matching a set of filter conditions. It responds to a change in the record’s overall state.

Conditional automations require Pro or Enterprise.