Skip to main content

Workflow Trigger: Contact Changed

The Contact Changed trigger automatically runs workflows when specific updates occur on a contact record, including tag changes, DND status updates, reassignment, and custom field modifications.

Updated over 3 months ago

What Can Trigger a “Contact Changed” Workflow

This trigger activates when any of the following changes occur on a contact record:

  • Tags are added or removed

  • Do Not Disturb (DND) is enabled or disabled

  • A contact is assigned or reassigned to a user

  • A custom field is populated

  • A custom field changes to a specific value

  • Address details (city, country, etc.) are updated

You can further control when the workflow runs by applying filters.

How to Set Up the Contact Changed Trigger

Step 1: Open Workflows

Navigate to Automations → Workflows, then create a new workflow or open an existing one.

Step 2: Add the Trigger

Inside the workflow builder, click Add New Trigger and select Contact Changed from the trigger list.

Step 3: Configure Filters (Optional but Recommended)

Use filters to define exactly which contact changes should activate the workflow.

Available filter examples include:

  • Assigned User

  • DND

  • Email

  • City or Country

  • Custom Fields

You may apply multiple filters to refine the trigger logic.

Step 4: Save the Trigger

Click Save Trigger to add it to your workflow.

Step 5: Add Workflow Actions

Once the trigger is saved, add the actions you want to run, such as:

  • Send Email or SMS

  • Add or Remove Tags

  • Enable or Disable DND

  • Assign or Reassign Contact

  • Send Internal Notifications

Common Use Cases

  • Tag-Based Automation: Trigger workflows when a tag is added or removed

  • DND Compliance: Stop or resume outreach when DND status changes

  • Sales Routing: Notify or assign a user when ownership changes

  • Custom Field Logic: Trigger onboarding, follow-ups, or status changes when a field updates

  • Data Cleanup: Take action when key contact fields are populated or corrected

Important Notes

  • This trigger only fires when a change occurs — it will not run on unchanged records.

  • Bulk imports can trigger workflows if Allow Triggers is enabled during import.

  • Use caution with bulk updates to avoid triggering large volumes of messages unintentionally.

FAQs

What types of updates activate the Contact Changed trigger?

Any supported change, including tag updates, DND changes, reassignment, address updates, or custom field changes.

Can I use multiple filters with this trigger?

Yes. You can apply multiple filters to narrow down exactly which changes should trigger the workflow.

How do I limit this workflow to specific contacts?

Use filters such as tags, assigned user, or custom field values to control which contacts qualify.

Why isn’t my workflow triggering?

Check that:

  • The workflow is published

  • Filters match the actual contact changes

  • The contact field being updated is supported by the trigger

Testing with a sample contact is recommended.

Can I edit the trigger after adding it?

Yes. You can edit the trigger at any time from the workflow builder to adjust filters or logic.

Does this trigger work during bulk imports?

Yes, only if “Allow Triggers” is enabled during the import. Use caution to avoid mass automation runs.

Did this answer your question?