“Opportunity Changed” Trigger with Event-Based Operators

This update is for Kyrios users building workflows based on opportunity updates who need precise control over when automations fire. Use this when workflows should respond only to actual field changes instead of every opportunity edit.

The Opportunity Changed trigger now includes event-based operators such as Has Changed, Has Changed To, Added, and Removed, depending on the field type.

Previously, the Opportunity Changed trigger evaluated opportunities like a filter. If an opportunity matched the condition, the workflow fired on any update to that opportunity. The trigger now detects field-level change events, allowing workflows to run only when a selected field changes.

This improves automation accuracy and prevents unnecessary workflow executions.

Standard opportunity fields now support event-based operators that trigger workflows only when the selected field changes.

Operator Availability by Field:

These operators allow workflows to trigger only when an opportunity is reassigned, moved to a different pipeline, changes status, or receives a lost reason—without triggering on unrelated updates like notes or value changes.

Example:
Trigger a workflow only when Assigned To changes to a specific user, instead of triggering on unrelated updates like notes or tags.

Custom opportunity fields now support event-based operators based on their field type, enabling reliable automation tied to custom data changes.

Operator Availability by Field Type:

Important Note:
Custom date fields are now supported in the Opportunity Changed trigger for the first time, allowing workflows to respond to date updates on opportunities.

Result:
Workflows can now respond reliably to updates in custom fields such as deal source, priority level, or internal status without triggering on unrelated edits.

This update prevents workflows from firing on unrelated opportunity edits and ensures automations run only when meaningful field changes occur.

Previously, a trigger like Assigned To = John fired every time any change was made to John’s opportunities, including note updates, tag changes, or value edits.

Using Assigned To → Has Changed To → John, the workflow now triggers only when the assignment actually changes to John.

This results in:

To use event-based operators, edit or create an Opportunity Changed trigger and select the appropriate operator for the field you want to monitor.

Steps:

Compatibility Note:
Existing workflows automatically continue using the previous Equals behavior. No workflows are broken or changed by this update.

Cause:
The trigger is still using an equality-based operator instead of an event-based operator.

Fix:
Update the trigger condition to Has Changed or Has Changed To for the relevant field.

Cause:
The field value did not actually change, even though the opportunity was updated.

Fix:
Confirm that the selected field is being modified during the update event. Event-based operators only fire when a value changes.