Workflow best practices, cost considerations, and troubleshooting
Build reliable automations in Omnifox: how to structure triggers and nodes, keep AI spend under control, and fix the most common failures.
Watch this step in the video · Best practices
Workflows run actions for you when something happens: a new message, a created contact, a won deal, and more. Done well they save hours; done poorly they create noise, loops, and needless AI costs. This guide collects the practices we use to keep flows reliable and affordable.
Requirements
- A workspace with the Workflows module enabled on your plan.
- Admin or workflow-editor permission.
Design best practices
- Start with the right trigger. In Workflows › Create flow, pick the most specific trigger you can (for example Incoming message filtered by channel, instead of Any activity). The narrower the trigger, the fewer wasted runs.
- Filter early. Put condition nodes right after the trigger to drop cases that don't apply before spending actions or AI tokens.
- One flow, one purpose. Avoid mega-flows with dozens of branches. Several small flows are easier to debug and disable.
- Name and document. Use clear names ("WhatsApp sales welcome") and add internal notes to each node.
- Test in draft. Keep the flow Inactive while building and use a test conversation before turning it on.
Cost considerations
Nodes that call AI (reply with agent, classify, summarize, translate) consume the workspace's AI credit. To keep it in check:
- Place conditions before any AI node so it only runs when it truly adds value.
- Reuse the agent's reply instead of chaining several AI calls for the same message.
- Tune the agent's token limit in its Behavior tab; shorter replies cost less.
- Review usage under Plans & billing, where you'll see the AI credit spent by the workspace.
Verification
After activating a flow, open its run history. Each run shows the trigger, the nodes it traversed, and whether it ended in success or error. Fire the real event (send a test message) and confirm a successful run appears.
If it doesn't work…
- The flow never fires: make sure it's Active and that the trigger filter (channel, tag, team) matches your test.
- It runs too often / loops: an action in the flow re-satisfies the trigger. Add a condition that excludes that case or switch to a more specific trigger.
- The AI node doesn't reply: check AI credit under billing and that the agent is published; with no credit, AI nodes are skipped.
- Action hits the wrong contact: keep everything workspace-scoped; never use global identifiers in conditions.
Tips
- Duplicate a working flow and adapt it instead of starting from scratch.
- Before a large campaign, test the flow against a handful of contacts.
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.