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.

Oct 30, 2026

Video chapters

  1. 00:00 Introduction
  2. 00:40 What a workflow is Read this step →
  3. 01:07 The workflow list Read this step →
  4. 01:35 Search and filter
  5. 01:53 Turn on, duplicate, export and delete
  6. 02:14 Three ways to create a workflow Read this step →
  7. 02:35 Editor tour Read this step →
  8. 03:12 Moving around the canvas
  9. 03:34 The palette: triggers and nodes Read this step →
  10. 03:58 Choosing the trigger
  11. 04:16 Trigger filters Read this step →
  12. 04:49 Stop when an agent replies, and trigger variables Read this step →
  13. 05:13 Adding nodes to the canvas Read this step →
  14. 05:37 Connecting nodes and branches
  15. 05:58 Business hours Read this step →
  16. 06:19 Send message Read this step →
  17. 06:49 Variables Read this step →
  18. 07:15 Asking a question Read this step →
  19. 07:59 One branch per option
  20. 08:28 Adding and removing tags Read this step →
  21. 08:51 Transferring to a person or a team Read this step →
  22. 09:20 The after-hours branch
  23. 09:49 Move, rename, duplicate, copy and delete
  24. 10:07 Undo, redo and auto-arrange
  25. 10:23 Validate, save and turn on Read this step →
  26. 10:45 Testing the workflow Read this step →
  27. 11:11 The live run
  28. 11:31 The run history
  29. 11:50 In real life: a patient writes from the website
  30. 12:17 The workflow in the inbox
  31. 12:42 If condition: a single rule Read this step →
  32. 13:07 Multiple branches
  33. 13:28 Contact has tag Read this step →
  34. 13:48 Date and time Read this step →
  35. 14:10 Detect language and agent in team Read this step →
  36. 14:39 Wait time and wait for an event Read this step →
  37. 15:13 WhatsApp templates and the 24-hour window Read this step →
  38. 15:34 Emails: to the customer and to the team Read this step →
  39. 15:53 Contacts and variables Read this step →
  40. 16:24 Conversation actions Read this step →
  41. 16:46 Respond with AI and AI classifier Read this step →
  42. 17:11 AI agents and workflows, together Read this step →
  43. 17:32 HTTP request Read this step →
  44. 17:50 Flow control Read this step →
  45. 18:14 Shortcuts for your team in the inbox Read this step →
  46. 18:31 Scheduled and incoming webhook Read this step →
  47. 18:53 CRM: triggers and nodes Read this step →
  48. 19:18 Appointments: triggers and nodes
  49. 19:45 Projects and Team Read this step →
  50. 20:08 Orders, payments, calls and more Read this step →
  51. 20:31 The template gallery Read this step →
  52. 20:53 Export and import Read this step →
  53. 21:15 Plans, limits and permissions Read this step →
  54. 21:38 Best practices Read this step →
  55. 21:56 Troubleshooting
  56. 22:16 Wrap-up

This is the complete guide to Workflows, in 54 chapters: the list, the editor, every trigger and every node, variables, how to test a workflow and read its history, templates, import and export, and how they connect with the inbox, CRM, appointments, AI, Projects and Team. The PDF manual has the same chapters with screenshots and steps.

What's new (October 31, 2026)

  • The board nodes Assign a person, Set a date, Append row to Google Sheets and Create/update HubSpot contact have their own form in the editor (Google Sheets and HubSpot are still “Coming soon” in Integrations).
  • History with filters by status, by workflow (this one or all in the workspace) and by dates, and a Retry button on failed runs: it runs the whole workflow again with the same trigger data and the current version, so steps that already succeeded are repeated.
  • Channel disconnected works for every channel type and doesn't repeat for the same channel within 1 hour.
  • Workflow identifier visible and editable in the trigger panel: it saves right away, is unique in the workspace and suggests “-2” if it's taken.
  • Appointment reminder: each workflow with “Hours before the appointment” gets its own window; empty uses the workspace's general reminder.
  • The trigger card no longer shows the technical key.

The PDF manual already includes these changes (version 1.1).

1. What a workflow is

A workflow always has the same shape: a trigger, which is the event that starts it, and then a chain of nodes: actions that do something, conditions that choose a path, and waits that pause the workflow.

For example, this one: when a patient misses an appointment, the workflow writes to reschedule it and creates a follow-up task for the front desk. Nobody has to remember: it just happens, every time.

Workflows live in Settings, Workflows, and each and every workspace has its own set of them.

2. The workflow list

This is the list. At the top, the total number of workflows in the workspace. Each card shows the name, the description, the switch to turn it on, and the pill with its trigger.

Below that, the numbers: how many nodes it has, how many times it ran and how many times it failed, the success rate with its color bar, and when it last ran.

If a workflow failed in the last seven days, the card flags it in red, shows you the last error and a link to open that run and see what happened.

3. Search and filter

You can search by name or description, and filter by trigger and by status: active, inactive, or with failures in the last seven days.

When a workflow is failing, this notice appears at the top with a button to see only those. And Clear filters takes you back to the full list.

4. Turn on, duplicate, export and delete

The switch on the card turns the workflow on or pauses it instantly. An inactive workflow never fires, but it keeps everything it has.

At the bottom of each card you have: edit; duplicate, which creates an inactive copy to test changes without touching the original; export, which downloads the workflow as a file; and delete, which asks you to confirm because it also erases its history.

5. Three ways to create a workflow

To create a workflow you have three paths: New workflow, which opens a blank editor; Templates, with workflows already built for common cases; and Import, to upload a workflow exported from another workspace or another account.

Whichever you choose, the workflow starts out inactive: nothing fires until you turn it on. Today we'll build one from scratch: the clinic's welcome and menu.

6. Editor tour

This is the editor. On the left, the canvas, where you draw the workflow. On the right, the panel that changes with what you're doing: the palette, a node's inspector, the trigger's, or the variables.

At the top, the workflow name, which you can change with a single click; the save status; the active pill; undo and redo; auto-arrange; variables; test; the run history; import and export; and the main button, Save.

And the How does it work button brings you to this video and the manual. While the workflow is missing something, the main button turns into Fix errors and a red notice at the top lists what's missing. Let's name it: Welcome and menu.

7. Moving around the canvas

On the canvas you move around by dragging the background with the mouse, like this, or with the arrow keys. With the mouse wheel or the buttons at the bottom you zoom in and out, this one centers the whole workflow on screen, and the lock freezes the canvas so nothing moves by accident.

In the corner you have the minimap, which shows the entire workflow and where you are. Really handy as the workflow grows.

8. The palette: triggers and nodes

The palette has two tabs. The Triggers tab holds every event that can start a workflow, grouped by topic: messages, conversations, contacts, system, calls, CRM, appointments, boards, time and Team.

Nodes holds the actions, the conditions and the waits. With the search box you can find any of them by typing part of the name. If a node needs a higher plan, it shows a lock and the plan name.

9. Choosing the trigger

It all starts with the trigger. We search for Message received and pick it: the trigger card appears on the canvas and, on the right, its settings.

A workflow has a single trigger. If you later swap it for another, Omnifox warns you that the previous trigger's filters may stop working.

10. Trigger filters

Filters decide when it fires and when it doesn't. In Message received you can limit it to a channel type, like web chat or WhatsApp, or to specific channels. If you check none, it fires on all of them.

You can also require the message to contain a keyword, or to be a certain type, like text, image or audio. And this checkbox is the key to a welcome: Only on the first inbound message of a conversation.

Careful with filters: if a message doesn't match them, the workflow simply doesn't fire, and leaves no error. If a workflow won't start, check its filters first.

11. Stop when an agent replies, and trigger variables

Under Behavior there's Stop this workflow when the agent replies. It's off by default: the agent can stop it by hand from the conversation. Turn it on if you want the workflow to step aside as soon as someone on your team writes or takes the conversation.

Further down, Available variables: the data this trigger brings, like the message text, the channel or the contact's name. One click copies them so you can paste them into your messages.

12. Adding nodes to the canvas

First we zoom out a little with the minus button and drag the trigger card over to the left, so that the whole workflow fits nicely on the screen.

To add a node, go to the Nodes tab and drag it onto the canvas, or click the card and it appears in the center of the view. We drag Business hours next to the trigger.

You can also right-click on the canvas and choose Add node, which has its own search box.

13. Connecting nodes and branches

To connect, drag from a node's output point, on its right side, to the next node's input point. That's how we join the trigger to Business hours.

Condition nodes have one output per branch, each with its own name. The connection keeps the branch name, and the workflow continues along it. To remove a connection, select it and press Delete, or use its menu.

14. Business hours

Business hours compares the current time with your workspace's business hours, in its time zone. It has two outputs: In hours and Out of hours.

The schedule isn't set in the node: there's just one for the whole workspace, in the workspace settings, and every workflow shares it. At Bright Smile it's Monday to Friday 9 AM to 7 PM, and Saturdays until 2 PM.

15. Send message

On the In hours branch we add Send message and connect it from that output. Clicking a node opens its inspector: at the top, an optional name to recognize it on the canvas, in this case Greeting, and below, its settings.

Under Channel you choose where it goes out: in the same conversation that fired the workflow, on a specific channel, by starting a new conversation, or on all of the contact's channels. For a welcome, the same conversation.

And we write the message. Notice the patient's name: it's a variable.

16. Variables

Variables are written inside double curly braces with a dollar sign: brace, brace, dollar, contact dot first name. When sending, Omnifox replaces it with the patient's real name. If a piece of data doesn't exist, it's left blank, never the code.

The Variables button opens the panel with every one you can use: the trigger's, the ones this workflow's nodes create along the way, like the answer to a question, and the system ones. One click copies any of them.

17. Asking a question

Now, Ask a question: it sends a question and pauses the workflow until the patient answers. We connect it after the greeting, call it Menu and write the question: How can we help you today? Then we pick the answer type: free text, options with buttons, number, date, phone, email or URL.

With Options you write the buttons, up to twenty characters each so they fit as WhatsApp buttons: Book a visit, Prices and Talk to someone. Each option becomes an output of the node. And the answer is saved in a variable, in this case option, to use later on.

If the answer isn't valid, you can retry with a message, and with the time limit you decide how many minutes to wait. That's why the node also has the Invalid and Timeout outputs.

18. One branch per option

We connect each option to its reply. The first one, Book a visit, goes to a message with the link to the clinic's booking page, where the patient picks the day and time that suit them best. We name this one Booking link.

For the second option, another Send message, connected to the Prices output, with the prices for the checkup, the cleaning and the whitening. The dollar sign types just fine. If a message looks like one you already have, you can also duplicate it with Control D and change only the text.

19. Adding and removing tags

After the booking link, Add tag gives the contact the tag Wants appointment. We connect it after the link, give it a name and check the tag. That way, when the front desk opens the inbox or Contacts, they'll know who wants an appointment.

You can pick an existing tag or type a new name, and it's created automatically. Remove tag works the same way, in reverse.

20. Transferring to a person or a team

The third option, Talk to someone, goes to Transfer to an agent, which we connect to that output. Under Action you can assign to a person, to a person within a team, to a team, or remove the assignment. We choose Assign to the team, and the Front desk team.

For a team you choose the logic: round robin, whoever has the fewest conversations, or manual. You can send the patient a notice, like Connecting you with the front desk, and the Stop other workflows checkbox makes sure no other workflow keeps writing in that conversation.

21. The after-hours branch

The Out of hours branch is still missing. From that Business hours output we add another Send message, call it After hours and write the clinic's opening hours, with a promise to reply first thing in the morning.

And then, Add tag once again, with the tag After hours, so the front desk sees these patients first when they open up in the morning.

So by day the patient gets the menu, and at night, an honest reply with the hours.

22. Move, rename, duplicate, copy and delete

Right-clicking a node gives you: rename, duplicate, copy and delete. The shortcuts work too: Control C and Control V to copy and paste, Control D to duplicate, and Delete to remove it.

You can drag the nodes around to arrange them, and hold down Shift to select several at once by dragging a box.

23. Undo, redo and auto-arrange

If you make a mistake, Control Z undoes and Control Y redoes, or use the arrows at the top.

And Auto-arrange lays out the whole workflow from left to right, with the branches in order. If you don't like it, just undo.

24. Validate, save and turn on

While anything required is missing, the node is flagged in red with what it lacks, and you can't save. Once everything is complete, the button says Save again.

We save. The workflow is still inactive: we turn it on with the pill at the top and save again. There's no autosave, so if you close with pending changes, the editor warns you.

25. Testing the workflow

Before you let it work, you test it. Test opens this window with two modes: Wait for the next event, which keeps the workflow watching for the next real message that comes in; or Run with recent data, which runs it right now on a conversation you choose.

Important: the test is real. It sends the messages and changes contacts for real. That's why it's best to use your own number or a test conversation, like this web chat one.

26. The live run

While it runs, the editor locks so nothing changes halfway through, and each node lights up as it executes. At the top, a pill shows the status: running, paused waiting for the answer, finished, or with errors.

At the bottom, the timeline with every step. Here the workflow paused at the question, waiting for the patient to pick an option.

27. The run history

The history shows the workflow's latest runs: whether they finished fine, failed, were canceled or are waiting, with the date and how long they took.

Pick one and you see every step, in order, with its result. If something failed, the error shows in red on the exact step. And if a run is still waiting, you can stop it from here.

28. In real life: a patient writes from the website

Now, in real life. This is the clinic's website with the Omnifox chat installed. Andrea, a patient, opens the chat and writes: Hello.

Instantly she gets the welcome with her name and the options menu, as buttons. She chooses Prices, and the workflow replies with the price list. Nobody at the clinic lifted a finger: the workflow did all the work, and if she had chosen Talk to someone, the conversation would have gone to the front desk.

29. The workflow in the inbox

In the inbox, Andrea's conversation shows everything the workflow sent. And while a workflow is active in a conversation, like this other one, still waiting for an answer to the menu, this notice appears at the top, with the button to stop it if a person wants to take over.

And the workflow's history keeps the complete run, step by step: the trigger, the business hours check, the greeting, the menu, the answer she chose and the message with the prices.

30. If condition: a single rule

Let's look at the rest of the nodes in a practice workflow, starting with the conditions. If, with a single rule, has two outputs: Yes and No. You pick a field, like the channel, the priority, a contact detail, the message text or your own variable; an operator, like equals, contains, greater than or is empty; and a value.

In the value you can also use a variable, to compare two pieces of data.

31. Multiple branches

Multiple branches is like several If conditions in a single node. Each branch has a name and rules, joined with And or Or: all must match, or one is enough. They're checked in order, and the first one that matches wins.

If none matches, the workflow continues along the default branch. And each branch is an output you connect to whatever you like.

32. Contact has tag

Contact has tag checks whether the contact has any of the tags you choose, all of them, or none, and continues along Yes or No. Here we check the VIP tag, to treat those patients differently.

A tip: with none, it works as a brake. For example, if the patient has the tag Do not message, the workflow stops there.

33. Date and time

Date and time checks the current moment, always in the workspace time zone. Under Operator you choose how: an exact day, before or after a date, between two dates, certain weekdays, certain days of the month, certain months, or a range of hours, even across midnight.

For example, to reply differently during a December promotion, or only on Saturdays.

34. Detect language and agent in team

Detect language works out which language the contact speaks, without asking: from the country code on WhatsApp, from the browser language on web chat, or from the text. Each language you check is a branch, and it can be saved to the contact's profile.

Agent belongs to team checks whether the agent assigned to the conversation, or one you pick, is in a team, any team or a specific one, and continues along Yes or No. Handy so you don't reassign someone who's already on the right team.

35. Wait time and wait for an event

There are two waits. Wait time pauses the workflow for minutes, hours or days, then continues through its only output. While it waits, it takes up nothing: it resumes on its own right on time. For example, a day after sending the link, ask if they managed to book.

Wait until an event happens is smarter: it pauses until the patient replies, or until the conversation is assigned, closed, resolved or gets a tag. It has two outputs: the event happened, or the time ran out. Always set a time limit, so that no abandoned conversation ever leaves the workflow waiting forever.

36. WhatsApp templates and the 24-hour window

On WhatsApp you can only write freely within twenty-four hours of the customer's last message. Outside that window, you need a message template approved by Meta.

Send WhatsApp template lets you choose the channel and the approved template, and fill in its parameters with variables, like the name or the appointment time. That's what we use for reminders.

37. Emails: to the customer and to the team

There are two email nodes. Send email to customer writes to the contact from your Email channel, with a subject and body, in plain text or HTML.

Notify the team by email is an internal alert: it goes out from Omnifox and only reaches people in your workspace, the ones you check.

38. Contacts and variables

Update contact writes data to the contact profile, like the email, the company or a custom field, even with the answer the patient gave: each row is a field and its value. Set variable stores values under any name you like, to use later on in the same workflow.

Find or create contact identifies them by phone or email and, if they don't exist, creates them; handy when the workflow comes from another system, through a webhook. And Look up prior conversation finds their last conversation and whether it had an assigned agent, to route them back to the same person.

39. Conversation actions

The palette also has several actions on the conversation. You can close it or mark it as resolved, reopen it, snooze it for a while, change its priority, leave an internal note that only your team sees, and request the satisfaction survey.

And Schedule message sets up a message to be sent later on, at an exact time or after a certain amount of time.

40. Respond with AI and AI classifier

Respond with AI has an AI agent reply at that point in the workflow, on its own or with an instruction from you, and you can send the reply or just save it in a variable.

The AI classifier reads the customer's message and picks one of your categories, like Booking, Prices or Complaint. Each category is an output, and if none fits, it continues along the No match branch. These nodes use AI credit.

41. AI agents and workflows, together

Assign AI agent hands the conversation over to one of your AI agents, which starts replying right away.

And the other way around: an AI agent can launch a workflow with its Trigger workflows tool, and the trigger The AI handed off the conversation fires when the AI passes a case to a person.

42. HTTP request

HTTP request connects Omnifox to any other system: you choose the method, the address, the headers and the body, with variables. The Test button sends it and shows you the response before you save.

It has success and error outputs, and the response can be saved in a variable to use in the following nodes.

43. Flow control

Control nodes keep big workflows tidy: Jump to another node goes back or skips ahead; Repeat for each item loops through a list; If it fails checks the previous step and continues along success or error.

Run in parallel opens several branches and Merge branches waits for all of them. And Call another workflow runs another of your workflows, whose trigger is Manual: perfect for reusing common steps.

44. Shortcuts for your team in the inbox

We switch the trigger to Shortcut. With it, the workflow becomes a button in the inbox: your team finds it in the conversation menu and runs it with one click.

For example, Send pre-cleaning instructions: one click and the patient gets everything, the same way every time.

45. Scheduled and incoming webhook

Scheduled runs the workflow on a timetable: every few minutes, every hour, every day at a set time, every week or every month, with shortcuts that build the rule for you. And Relative date is for alerts like three days before something is due.

Incoming webhook gives you your own address: when another system sends it data, the workflow fires with that data.

46. CRM: triggers and nodes

With the CRM, on the Triggers tab you search for deal and you see all of its events: workflows fire when a deal is created, changes stage, is won or lost, goes several days without activity, or gets stuck in a stage.

And the nodes create or update deals, assign an owner, log an activity or create a follow-up task. This workflow here turns every single new patient into a brand new deal in the Treatments pipeline.

47. Appointments: triggers and nodes

With the calendar, searching for appointment shows its triggers: appointment created, canceled, rescheduled, confirmed, reminder, the patient didn't show, appointment attended, a slot opened up, and someone joined from the waitlist.

Appointment nodes book, reschedule, cancel, confirm, mark a no-show, add someone to the waitlist, check availability or block time on the calendar. This workflow sends the reminder on WhatsApp one day before.

48. Projects and Team

With Projects: when a treatment is accepted, this workflow creates the patient's card on the Treatments in progress board, linked to the deal. There are also nodes to update cells, complete tasks or move them between groups, plus board triggers.

And with Team, internal communication: post in a space, send a direct message, create a reminder or schedule a message; and triggers like you were mentioned or message posted.

49. Orders, payments, calls and more

If you sell through the catalog, there are triggers for orders, abandoned carts and payments, with nodes to send the cart link or change the order status.

And with calls: missed call, after hours, recording ready, voicemail, or phone menu option. For example, after a missed call, send them a message on WhatsApp right away. Call triggers are included in the plans that come with calling.

50. The template gallery

In Templates you'll find ready-made workflows: lead follow-up, welcomes, team alerts, projects when a deal is won, appointment confirmations and reminders.

When you use one, it's created in your workspace, inactive. Check what it says needs completing, like the board or the Team space, adjust the texts, and turn it on.

51. Export and import

Import/Export, in the editor, gives you the workflow as text to copy or download. When you import it into another workspace, Omnifox asks you to match whatever doesn't exist there, like channels, teams, tags or agents.

You can add it alongside the current workflow or replace it entirely. From the list, the Import button does the same with a file, and the workflow arrives inactive.

52. Plans, limits and permissions

Each plan includes a number of runs per month, from one thousand on Lite up to fifty thousand on Escala. At eighty percent we let you know by email, and when you hit the cap, workflows pause until next month.

To create and edit workflows you need the manage workflows permission; anyone who can only view them sees the list and the editor in read-only mode. On your phone, the editor opens read-only, step by step.

53. Best practices

A few best practices: name every node, start with short workflows, and always test them with your own number before turning them on.

Use Only on the first inbound message for welcomes, always set a time limit on waits, and check the history and the failing workflows every week.

54. Troubleshooting

The workflow won't fire? Check that it's active and saved, and that the event matches the trigger filters: a filter that isn't met leaves no error.

It stopped halfway? Open the history: the step in red tells you exactly what failed. A WhatsApp message didn't arrive? It may be the twenty-four-hour window: use a template.

Was this helpful?

Related articles

Message us on WhatsApp