Trigger: Stage/Status Changed

The Stage/Status Changed trigger (record.stage_changed) fires a workflow when a record — a CRM deal, a task, a board item — moves from one column or stage to another. It's the base trigger for automating any staged process: sales pipelines, support Kanban boards, or approval flows.

When it fires

It fires as soon as the column/stage change is saved, carrying both the old and new values.

Requirements

• A record with a stage/status-type column configured (a CRM pipeline or a status column on a board).

Trigger configuration

• Record type: leave blank for any type, or set one (deal, task, item) to narrow the trigger.

Available variables

• $trigger.column_old — Previous column value
• $trigger.column_new — New column value
• $record.object_type, $record.object_id, $record.workspace_id

Example

A workflow triggered by record.stage_changed with Record type = deal and a condition where $trigger.column_new equals "Proposal sent": the workflow automatically sends the customer a WhatsApp message with the proposal link and notifies the assigned salesperson.

Tips

• If your case is specifically a CRM deal moving to "won" or "lost", use the semantic deal.won / deal.lost triggers instead of hand-building the condition on this generic one.
• For boards, there's also board.column_changed for non-status-type columns — pick whichever matches the column type you're moving.

Troubleshooting

If the workflow doesn't distinguish stages correctly, check that you're comparing against the exact column name (case/accent-sensitive) as configured in the pipeline or board.