Who This Is For / When to Use
This feature is for Kyrios users who need workflows to react immediately when contact location data is updated.
Use this trigger when address changes should:
Notify internal teams
Update territory or routing logic
Start location-based automations
Sync downstream systems
What Changed in the Contact Changed Trigger
The Contact Changed trigger now includes address fields as filterable conditions.
Supported address fields include:
Street Address
City
Country
Postal Code
Workflows can now trigger the moment one or more of these fields changes, without requiring additional If/Else actions or custom-field tracking.
How Address-Based Contact Changed Triggers Work
The Contact Changed trigger evaluates whether selected address fields have been updated.
When the defined condition is met:
The contact is enrolled in the workflow
Workflow actions begin immediately
Each address field can be evaluated independently or combined with multiple filters.
How to Use Address Fields in a Contact Changed Trigger
Step 1: Open or Create a Workflow
Go to Automation → Workflow Builder, then open an existing workflow or create a new one.
Step 2: Add or Edit a Contact Changed Trigger
Add a new Contact Changed trigger or edit an existing one.
Step 3: Add Address Filters
Click Add filters, then select one or more address fields:
Street Address
City
Country
Postal Code
Choose an operator such as Has changed or Has changed to.
If required, specify the new value the field must change to.
Step 4: Save and Publish
Save the trigger and publish the workflow.
The workflow will now run whenever the selected address fields change.
Supported Operators for Address Fields
Address fields support standard Contact Changed operators, including:
Has changed
Has changed to
These operators allow workflows to respond either to any change or to a specific new value.
Why This Update Matters
Previously, reacting to address updates often required:
Additional If/Else logic
Custom duplicate fields
Manual data checks
Native address field support simplifies workflow design and ensures automations run exactly when location data changes, with no workarounds.
Example Use Cases
Service Area Validation
Trigger an internal alert when Postal Code changes to a serviced or non-serviced area.
Sales Territory Updates
Recalculate ownership or routing when City or Country is updated.
Data Correction Tracking
Automatically add a note or tag when a Street Address is corrected or updated.
Common Issues and Fixes
Workflow does not trigger after an address update
Cause: The selected address field did not actually change value.
Fix: Confirm the field value changed and matches the selected operator.
Trigger fires too often
Cause: Multiple address fields are updated simultaneously.
Fix: Narrow the trigger to only the required address field or use Has changed to.
Address filter option not visible
Cause: Trigger type is not set to Contact Changed.
Fix: Ensure the trigger type is Contact Changed, not Contact Created or another trigger.