Workflows automate repetitive work: when something happens, Talvo runs the steps you drew.
The canvas
Open Workflows → New workflow to design on a canvas:
- A trigger starts the flow — a conversation is created, a message arrives, or a conversation is resolved.
- Conditions branch the path, with a green true route and a red false route.
- Actions do the work: assign a teammate, set priority, add a tag, send a reply, add an internal note, or enroll a sequence.
Drag from a node's port to the next node to connect them.
Shown with our demo workspace.
Conditions in detail
A condition can test the channel, the priority, a tag, or a keyword in the message or subject. Conditions on a single node are combined with AND — every one must match for the true branch to be taken.
To express OR, use two rules rather than trying to bend one node into doing both.
Actions run in order
Actions on a node run top to bottom, so sequence them the way you would do them by hand: assign first, then set priority, then reply. If an action cannot be applied — for instance assigning to someone who has since been removed from the workspace — the run records it and continues rather than abandoning the rest.
Examples
- Flag refunds: a message contains "refund" → set priority to urgent, add a note, assign to Billing.
- Welcome new chats: a conversation is created → send an instant reply.
- Close the loop: a conversation is resolved → enroll the contact in a short follow-up sequence.
Watching what happened
Every execution is recorded in the workflow's run history: which trigger fired, whether conditions matched, and which actions ran. When a workflow "does nothing", the run history is the first place to look — usually a condition did not match what you expected.
Workflows versus routing rules
Routing rules answer one narrow question — who should own this — and run only when a conversation is created. Workflows run on more triggers and take an ordered list of actions. If you only need assignment, a routing rule is simpler.
Turning one off
Toggle a workflow off at any time. Disabling keeps its history; deleting does not.
