Trigger types reference

A trigger defines when a workflow fires. Every workflow has exactly one trigger. Here's a complete reference of all available trigger types.

Data threshold

Fires when a metric crosses a specific value.

• Metric: choose from NPS, CSAT, or any numeric aggregation (avg, sum, count)
• Operator: greater than, less than, equal to, greater/equal, less/equal
• Value: the threshold number
• Window: time window in hours to evaluate (e.g., last 24 hours)

Example: "Fire when average CSAT drops below 3.5 in the last 7 days."

Row ingested

Fires when new data rows arrive (via upload, connector sync, or webhook).

• Filter conditions: optionally restrict to rows matching specific criteria
• Execute per row: toggle to fire the workflow once per matching row (useful for individual notifications) vs. once per batch

Example: "Fire when a new support ticket arrives with priority = Urgent."

Insight generated

Fires when the AI Insights engine produces a new insight.

• Minimum priority: only trigger for insights at or above a priority level (e.g., high or urgent)
• Category filter: optionally restrict to specific insight types (friction, variance, theme)

Example: "Fire when an urgent friction insight is generated."

Action event

Fires when an action changes state.

• Sub-events: created, status changed, priority changed, assigned, category changed, updated, deleted
• Conditions: filter by priority, status, category, or assigned user

Example: "Fire when any action's status changes to Blocked."

Action deadline

Fires as a reminder before an action's end date.

• Remind before: number + unit (e.g., 2 days, 4 hours)
• Repeat: fire again if the action is still open
• Filters: restrict to specific statuses or priorities

Example: "Fire 24 hours before an action's deadline if it's still In Progress."

Action overdue

Fires when an action passes its end date without being resolved.

• Overdue by: how long past the deadline before triggering
• Repeat interval: fire again periodically while still overdue
• Exclude statuses: don't fire for actions already resolved or closed

Example: "Fire when an action is 48 hours overdue, repeat every 24 hours."

Comment added

Fires when someone adds a comment to an action.

Example: "Notify the action's assignee whenever a new comment is posted."

Sync completed

Fires when a data connector sync finishes successfully.

• Minimum rows: only trigger if at least N rows were synced

Example: "Fire when the Google Sheets sync completes with more than 100 new rows."

Sync failed

Fires when a connector sync encounters an error.

Example: "Send a Slack alert when the daily data sync fails."

Manual

No automatic trigger - the workflow only runs when you click Run Now.

Example: "A monthly cleanup workflow that you trigger manually at the end of each period."

Next steps

• See what action steps you can pair with these triggers
• Learn about conditional branching to add logic