React to Record Updates with the Contact Changed Trigger

Contacts are always changing: new tags, updated fields, a new owner. The Contact Changed trigger lets a workflow watch for those edits and respond right away.

What it watches

The trigger fires when a tracked part of a contact record is updated. You choose which parts using filters:

• Custom Field: a specific field changing, such as Website or Preferred Service.
• Tags: a tag being added to the contact.
• DND: the do-not-disturb setting changing.
• Contact type: a lead becoming a customer.
• Assigned user: the contact being given to a different team member.

You can add several filters so the workflow reacts to any of the selected changes. Use the dedicated Contact Tag trigger when you need to react to a tag being removed, because Contact Changed focuses on new values rather than removals.

Set it up

1. Open Automation > Workflows and create a workflow.
2. Click Add New Trigger and select Contact Changed.
3. Give it a purposeful name, for example "Website address updated".
4. Click Add filters and choose the field, tag or setting to track.
5. Save the trigger, add actions, and publish.

Examples

• Assigned user changed: notify the new owner and create a first-contact task.
• Custom field updated: when "Preferred Service" changes, send a targeted offer.
• Contact type becomes Customer: stop sales messages and start onboarding.

Avoiding repeat runs

Each qualifying change can start the workflow again if re-entry is allowed. To keep it calm:

• Narrow the filters to the exact change you care about.
• Add a Condition step that checks whether the work was already done.
• Use a short Wait step so rapid-fire edits are handled once.

Good to know: Changes made by other workflows count too, so be careful not to create a loop where a workflow edits the field it is listening to.