Workflow triggers catalog

Learn which events can start a workflow automatically in Omnifox.

Jun 22, 2026

Watch this step in the video · The palette: triggers and nodes

Every workflow starts with a trigger: the event that kicks off the automation. Choosing the right trigger is the first and most important step when designing a flow. This article summarizes the families of triggers available.

How a trigger works

The trigger is the first node of the flow. When the event it defines happens (for example, "a new message arrives"), the workflow runs for that contact or conversation, going through the action and condition nodes you placed afterward.

Trigger families

Omnifox groups triggers into categories by the module that originates them:

  • Conversations and messages: new inbound message, conversation opened, conversation closed or resolved, conversation assigned, first contact.
  • Contacts / CRM: contact created, contact updated, custom field changed, lifecycle stage change.
  • Deals: deal created, deal stage changed, deal won, deal lost.
  • Team: internal events from the team communication module.
  • Projects / Boards: item created or assigned on a board, task created from a deal, item inactivity.
  • Time / scheduling: date-based or inactivity triggers (for example, "no activity for X days").

How to pick the trigger

  1. In the workflow editor, create a new flow.
  2. Select the trigger category.
  3. Choose the specific event within that category.
  4. Configure the trigger filters (for example, only for a certain channel, stage, or pipeline) so the flow doesn't fire too often.

Best practices

  • Narrow the trigger with filters: a too-broad trigger runs the flow more than needed.
  • One flow, one purpose: avoid hanging too much logic off a single trigger.

Tip: review the full trigger catalog before designing a flow. Sometimes there's a more specific event than the one you planned to use, and that simplifies the whole workflow.

Was this helpful?

Related articles

Message us on WhatsApp