Contact triggers (created, field updated, no response)
Fire automations when a contact is created, a record field changes, or the contact stops replying.
Watch this step in the video · The palette: triggers and nodes
Contact triggers start an automation from the contact record itself, not from a conversation. Use them to welcome someone new, react when a CRM field is filled in, or re-engage a contact who went quiet. This article covers the three contact triggers.
Available triggers
- Contact created — fires when a brand-new contact enters the workspace. Filter by Source channel type to tell, say, WhatsApp apart from a manual entry. It exposes variables like the source and the channel that created the contact.
- Contact field updated — fires when a specific field on the record changes. You pick the Field (required) and, optionally, Old value equals, New value equals or Only when the old value was empty (perfect for "filled in for the first time").
- Contact no response — fires when a contact has gone a while without replying, ideal for re-engagement or wrapping up the cycle.
Requirements
- A plan with Automations enabled.
- Permission to manage automations in the workspace.
Steps
- Open Automations and click New automation → Start from scratch.
- In the Trigger panel, open Choose how it starts and select, for example, Contact created.
- In Settings tune the filters. For Contact field updated, choose the Field to watch; keep it as specific as possible.
- Connect your Actions: send a welcome message, add a tag, notify the team or log an activity.
- Insert tokens from Available variables (source, channel, contact data) into your action text.
- Save and click Activate.
Verify it
- Use Test to fire it with a sample contact, then check Run history → View trace.
- Create a real contact or edit the watched field and confirm the run shows as Completed.
If it doesn't work
- Make sure the automation is Active.
- In Contact field updated, remember the Field is required: without it, nothing fires.
- If you used New value equals, confirm the value matches exactly (case and spaces count).
- For Contact created, a wrong Source channel type filter drops the new contact. Leave it empty to accept all.
- Seeing Paused by limit? You hit the plan's run cap.
Tips
- Tick Run only once per contact when the option is available, so you don't greet the same person twice.
- Combine Only when the old value was empty with a greeting: it fires only the first time a key field (email, city, etc.) is filled in.
Related articles
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.