Contact Changed Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Contact Changed trigger fires whenever a contact's details update, including tags, custom fields, DND status, or assigned user. Use it to automate follow-ups, notifications, and segment-specific actions when contact data changes.

The Contact Changed workflow trigger fires whenever a contact record is updated. It is the right trigger when you need automation to react to data changes rather than to a brand-new contact being created.

What it watches for

Tags changed — a tag is added or removed (for example, "Interested Customer" added).
DND status changed — Do Not Disturb is enabled or disabled.
Assigned user changed — the contact is reassigned to another team member.
Custom field updated — any custom field on the contact record is modified.

When to use it

Use Contact Changed when the action you want depends on a state change, not on the contact existing. Examples:

Send a follow-up email when a tag like "Hot Lead" is added.
Stop outbound messaging when DND is turned on.
Notify a sales rep when a contact is reassigned to them.
Send a targeted offer when the "Preferred Service" field is updated.

How to set it up

Go to Automations > Workflows.
Click + Create Workflow > + Start from scratch.
Click Add New Trigger and search for Contact Changed.
Give the trigger a descriptive name (for example, "Website Address Updated").
Set filters for the kind of change you care about: Custom Field, Tags, or DND.
Save the trigger and add the workflow actions you want it to run.

Filter notes

Each filter type narrows the trigger to a specific change. If you want one workflow to react to several change types, add multiple filters under the same trigger — they evaluate as OR conditions, so any matching change fires the workflow.

Frequently Asked Questions

What types of contact changes can fire this trigger?

Tags added or removed, contact type changed, custom field updates, assigned user change, and DND status changes. Each can be filtered independently.

Can a single workflow react to multiple change types?

Yes. Add multiple filters to the trigger. The workflow fires when any of the configured changes occur, so you can handle several events with one automation.

If a contact's data changes multiple times, will the workflow fire each time?

Yes. Each qualifying change fires the trigger independently. Use re-entry settings on the workflow if you need to limit how often a single contact can run through it.

What is the difference between Contact Changed and Contact Created?

Contact Created fires once when a new contact record appears. Contact Changed fires when an existing contact's data is updated. Use Contact Created for onboarding flows and Contact Changed for state-driven automation.