Trigger: Lifecycle Stage Updated

The Lifecycle Stage Updated trigger used to react whenever a conversation's assigned lifecycle stage changed (e.g. from "New lead" to "Negotiating" to "Customer"), including whether the new stage was terminal.

Important note: the lifecycle-stage feature was retired from Omnifox in June 2026. This trigger no longer appears in the palette for building new automations, and nothing in the system writes a lifecycle stage anymore — so it never fires on new workspaces. It's documented here only to explain older workflows that still reference it and continue to open without error in the editor.

What it used to do

• Filtered by source stage and target stage, and whether the new stage was terminal.
• Exposed variables like $lifecycle.previous_stage_name, $lifecycle.new_stage_name, $lifecycle.is_entering_terminal and $lifecycle.updated_by_source.

Variables (historical)

• $lifecycle.previous_stage_id / previous_stage_name / previous_stage_color
• $lifecycle.new_stage_id / new_stage_name / new_stage_color
• $lifecycle.is_entering_terminal, $lifecycle.updated_by, $lifecycle.timestamp
• Conversation and contact variables

Recommended alternatives today

• For conversation status tracking: Conversation resolved, Conversation closed, or Conversation marked pending.
• For sales stages: the Deal triggers (Deal won, Deal lost, Deal changed stage) in the CRM module.
• For contact tracking: Tag added / Contact field updated.

Troubleshooting

If you have an old workflow using this trigger and it stopped running, that's expected — the data source that fed it (lifecycle_stage_id) is no longer updated anywhere. Migrate that workflow to one of the alternative triggers listed above.