Anatomy of a workflow: triggers, nodes, conditions, and variables
Learn the four building blocks of every Omnifox automation and how they fit together on the visual canvas.
Watch this step in the video · What a workflow is
An Omnifox workflow (automation) is a visual sequence that reacts to something happening in your business and runs actions for you. Every workflow, simple or advanced, is built from the same four pieces. Understanding them lets you read and build any flow with confidence.
Where you build them
Open Workflows in the side menu and click New workflow to open the visual canvas (flow editor). There you drag and connect the pieces.
1. The trigger
This is the event that starts the flow: the "when?". Every workflow has exactly one trigger at the start. Omnifox offers dozens, grouped by category —conversation, contact, CRM, projects, team, webhook—. Examples: Incoming message, Conversation resolved, Deal with no activity, Webhook received. Without a trigger, the workflow can't turn on.
2. The nodes (actions)
These are the steps the flow runs: the "what does it do?". They chain one after another from the trigger. Common nodes:
- Add tag / Add note to the conversation.
- Assign agent or assign AI agent.
- Create deal, create task, create appointment.
- Wait (delay) a fixed duration before continuing.
- Notify a person or publish to Team.
3. Conditions (Yes / No branches)
The If node evaluates a question and branches the flow into two paths —Yes and No— based on the result: the "depends on what?". For example: is the deal amount over $500? → on Yes reassign to a senior rep; on No send a standard email. You can nest conditions for richer logic.
4. Variables
These are data that travels through the flow and that nodes read or produce: the "with what information?". They're written with the $ prefix, e.g. $last_agent_id, $detected_language, or $last_conversation_id. Many nodes expose variables (they generate them) that later nodes can use in their conditions or messages.
How they fit: an example
- Trigger: Incoming message.
- Node: Detect language → exposes
$detected_language. - Condition (If): is
$detected_language"pt"? → on Yes assign to the Brazil team; on No continue the normal flow. - Node: Assign agent and Add tag.
Verify
- Click Turn on and check the Runs tab: each time the event happens you'll see a run with the path it took.
If it doesn't work
- It doesn't run: confirm the workflow is on and has a valid trigger.
- It takes the wrong branch: review the If node's condition and that the variable holds the expected value.
- A variable comes out empty: make sure the node that exposes it sits before the node that uses it.
Tips
- Start with a 2-3 node flow and test it before adding conditions.
- Use clear names on each node so the canvas reads like a sentence.
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.