Trigger: Contact Field Updated

What it is

Fires when a standard contact field's value changes: first name, last name, display name, email, phone, company, job title, city, country, locale, sentiment, avatar, or notes. It does not currently cover custom fields you create in Settings — only this fixed list of standard fields.

When to use it

• Notify Sales when a contact's "Company" field gets filled in.
• Trigger a sequence when "Email" or "Phone" changes.
• Sync changes to these fields to an external system.

Requirements

• The change must be on one of the supported standard fields (see list above).
• Workflows enabled.

Available variables

• $contact.* (all contact data)
• $change.field — the name of the field that changed
• $change.old_value / $change.new_value
• $change.updated_by / $change.updated_by_source
• $change.timestamp

Configuration (filters)

• Field (required): pick the specific standard field to watch (email, phone, company, job_title, city, country, locale, sentiment, notes, first_name, last_name, display_name, avatar_url).
• Old value equals / New value equals: optional, for exact matches.
• Only when the previous value was empty.
• Change source: agent, API, another workflow, contact merge.

How to set it up

1. Open Workflows → create a new workflow.
2. Open the "Contacts" category.
3. Drag "Contact field updated" onto the canvas.
4. Pick the standard field to watch (required) and, optionally, a specific value.
5. Connect the action: notification, tag, assignment, etc.
6. Save and activate the workflow.

Example

When an agent fills in a contact's "Company" field for the first time (from_empty = true) with "Acme Corp", the workflow instantly notifies the Sales team with $contact.display_name and $change.new_value.

Tips

• Use "Only when the previous value was empty" to catch the first time a field gets filled in, without re-alerting on every later edit.
• If you need to react to a custom field (not standard), this trigger doesn't detect it yet; contact support or use a different approach (e.g. check the field inside a workflow triggered by another event).

Troubleshooting

• If it doesn't fire, confirm the field you edited is one of the standard supported fields (see the list under "What it is") — custom fields created in Settings don't fire this event today.
• Also verify the "Field" filter exactly matches the field you changed.