Triggers - Blue Docs

A trigger is an event or condition that sets off an automation. For instance, a trigger could be the completion of a record, a change in a record’s assignee, or a change in a custom field. When this predefined condition is met, the automation is activated.

Event Triggers

These are the event-based triggers available for automations in Blue:

Record Events

Record Created: Triggers when a new record is added to the workspace. Useful for initiating follow-up actions or notifications related to new tasks or entries. This also triggers when there is a new form submission.
Record Moved to List: Activates when a record is transferred from one list to another within the workspace, indicating a change in its stage or status.
Record Marked as Complete: Triggers when a record’s status is updated to complete, signalling the end of a task or process.
Record Marked as Incomplete: Activates when a record previously marked as complete is reverted to an incomplete status.
Record Copied/Moved from Another Workspace: Activates when a record is brought into the current workspace from a different one, helpful in tracking cross-workspace workflows. The trigger applies whether the record is manually moved or copied by a user, or automatically transferred through another automation.
Record Added to Another Workspace (Enterprise): Triggers when a record is added to another workspace, enabling multi-workspace workflow tracking.

Field Changes

Assignee Added: Triggers when a new assignee is added to a record, indicating their responsibility for that task or item. You can optionally filter by specific assignees.
Assignee Removed: Activates when an assignee is removed from a record, signifying a change in task responsibility.
Date Has Changed: Triggers when the due date of a record is set or altered, which can be critical for time-sensitive tasks.
Date is Removed: Activates when a record’s due date is cleared, possibly indicating a change in priorities or timelines.
Date Has Expired: Triggers when a record’s due date passes without completion, highlighting potential delays or oversights. This trigger can also monitor custom date fields, not just the default due date. You can configure the timing to trigger before, after, or at the moment of expiration, and optionally restrict it to only incomplete records.
Tag Added: Activates when a new tag is added to a record, useful for categorization and tracking changes in task attributes. You can filter by specific tags.
Tag Removed: Triggers when a tag is removed from a record, indicating a change in its categorization or properties.
All Checklist Items Marked as Complete: Activates when every item in a record’s checklist is checked off, indicating the completion of all sub-tasks.
Checklist Item Marked as Incomplete: Triggers when any checklist item is marked incomplete, signalling unfinished sub-tasks.
Custom Field Value is Set: Triggers when data is written to a specific custom field in a record. This works with checkboxes, single select, and multiple select custom fields.
Custom Field Value is Removed: Activates when data is removed from a specific custom field in a record.
Color Added: Triggers when a color is assigned to a record, indicating priority, progress, or categorization. You can filter by specific colors.
Color Removed: Triggers when a color is removed from a record, signaling a change in status or priority.
Button Clicked: Triggers when a user clicks a button custom field on a record. This enables interactive workflows where users can manually trigger automations by clicking designated buttons within records.

Scheduled Triggers

On Schedule: Runs the automation on a recurring schedule. You can configure the frequency (daily, weekly, monthly, or yearly), the time of day, and the timezone. Scheduled automations apply their actions to records that match the automation’s filter criteria at the time the schedule fires.

Conditional Triggers

When Conditions Met: Monitors records and triggers when they start matching (or stop matching) a set of filter conditions. This allows you to build automations that react to the overall state of a record rather than a single event.