Imagine having a helper that automatically does important tasks whenever a contact's information changes. That's exactly what the "Contact Changed" workflow trigger does in ZipLeads. It keeps track of changes, like new tags being added, updates to custom fields, or a contact being assigned to someone. It then performs actions based on those changes. Let's look at why it's useful and how to set it up step by step.
What is the "Contact Changed" workflow trigger?
The "Contact Changed" workflow trigger activates whenever a contact's details are updated. For example:
Tags Changed: If a tag like "Interested Customer" is added, the workflow can send a follow-up email.
DND Status Changed: If a contact turns on "Do Not Disturb", the workflow can stop sending messages.
Assigned User Changed: If a contact is assigned to a new sales rep, the workflow can notify them.
Custom Fields Updated: If a field like "Preferred Service" is updated, the workflow can send targeted offers.
This trigger helps your business respond quickly and keeps everything organised by automating repetitive tasks.
Why use the "Contact Changed" workflow trigger?
The "Contact Changed" trigger is like having a smart assistant. It tracks updates to contact details and reacts instantly, so you stay on top of changes.
It saves time by handling tasks like sending emails or assigning follow-ups automatically.
It improves customer service by making sure contacts get faster, more relevant responses.
It creates opportunities by helping you act on new leads or changes, like following up on updated business information.
How to set up the "Contact Changed" workflow trigger
Follow these steps to set up the workflow trigger.
Start a new workflow
Go to the Automations section in your account. Click Workflows.
Create the workflow
Click the + Create Workflow button at the top right, then click + Start from scratch.
Add the trigger
Click Add New Trigger and search for "Contact Changed".
Name the trigger
Give it a descriptive name, like "Website Address Updated".
Set filters
Decide which contact changes will activate the trigger:
Select Custom Field if you want to track changes in a specific field, like "Website".
Choose Tags if you want the workflow to react to added or removed tags.
Use DND if the workflow should respond to changes in the "Do Not Disturb" setting.
Frequently Asked Questions
Q. What types of contact changes can trigger the "Contact Changed" workflow?
The "Contact Changed" trigger can activate based on various contact updates, including:
Tags added or removed – for example, if a contact is tagged as "Hot Lead", trigger a sales follow-up.
Contact type changed – for example, if a contact goes from a "Lead" to a "Customer".
Custom field updates – for example, if a contact's "Preferred Service" is updated, send targeted promotions.
Assigned user change – for example, if a contact is reassigned to a new sales rep, notify the rep straight away.
DND status change – for example, if a contact turns on "Do Not Disturb", stop all outgoing messages.
Q. Can I track multiple contact changes within a single workflow?
Yes. You can add multiple filters under the "Contact Changed" trigger to track different types of changes at the same time. For example, you can set the workflow to trigger when either a tag is added OR a custom field is updated, so the automation responds to multiple events.
Q. What happens if a contact's details change multiple times? Will the workflow trigger each time?
Yes, the workflow will trigger each time a tracked change happens. To prevent unnecessary actions (like multiple emails being sent), you can:
Use workflow conditions to check whether the action has already been performed.
Apply filters so it only triggers on specific changes.
Add time delays to avoid excessive automation.
Q. Can I trigger actions based on a deleted tag or an old value being removed?
No. The "Contact Changed" trigger detects new updates but doesn't track removed values. If you need to automate actions based on a tag being removed, consider:
Using an "If/Else" condition to check whether a contact still has a specific tag.
Manually monitoring tag removals and triggering a different workflow accordingly.