For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/workflows.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.
Get a workflow running
A workflow is a graph: one trigger, then nodes. Building it under Work Flows is not enough. A phone trigger does nothing until the workflow is on for that agent under Skills - Tools & Workflows. An unsaved canvas does not run.
The node catalog (API, email, SMS, HubSpot, branches) is Workflow Nodes. This section is when the graph starts.
Why setup matters
Section titled “Why setup matters”Three things have to be true or the graph is decoration:
- A trigger sits on the canvas.
- You clicked Save & go live (or saved a version).
- For a phone trigger - the workflow toggle is on for this agent under Business Workflows.
Run test in the builder proves the graph. It does not prove a live caller will hit it.
Open Work Flows
Section titled “Open Work Flows”Sidebar - Work Flows. Page line: Automations that connect systems, fetch live data, send messages and run logic — triggered by calls, schedules or events.
Empty state: Build your first workflow. Button: + Workflow.

+ Workflow opens Create new workflow (Name it now — configure capabilities in the builder.). Beta note: limited to 5 workflows during beta. Enter Workflow name, then + Create workflow (or Cancel).

You can also + Add workflow from the agent’s Skills - Tools & Workflows - that creates and lists it under Business Workflows.
Copy or move a workflow to another company
Section titled “Copy or move a workflow to another company”In Copy workflow, turn off Copy to same company, choose Copy or Move, then pick the Target company: the list opens with every company you can send it to, A to Z, and typing narrows it. Move is refused while an agent here still uses the workflow as a tool, and only the workflow’s owner can move it.
Which trigger
Section titled “Which trigger”In the builder, + Add Trigger opens Phone Triggers (and more as you scroll):

HubSpot created / property-changed, WooCommerce, and similar event triggers appear in the same catalog when those integrations are connected.
AI Response to Caller only exists under a live-audio trigger (Start, Connect, During, Keyword, Key Pressed) - not End or Missed. Transfer Call only under Start, Connect, or During.
First setup - one Call Start, attach, prove it
Section titled “First setup - one Call Start, attach, prove it”-
Sidebar - Work Flows - + Workflow
Name it after the job (for example Caller lookup). + Create workflow.
-
+ Add Trigger - Call Start Trigger
Phone Triggers. Leave it empty - this trigger has no required fields.
-
Save & go live (top right)
Use Save as version when you want a named checkpoint. Run a builder test if available - dry-run (Don’t send messages, on by default) keeps Email, SMS, Viber, Slack and Google Chat from sending and shows where each message would go.
-
My Agents - this agent - Skills - Tools & Workflows
Under Business Workflows (
N/M active), turn the row on. Or use + Add workflow if you created it from here.
index-attach -
A real inbound call (or Try this agent)
Open Calls. If nothing ran, the toggle is off, you tested a different agent, or you never saved.
Workspaces are on a beta workflow cap (Limited to 5 workflows during beta). If Create workflow is blocked, delete an unused graph or wait for the cap to lift.
Troubleshooting
Section titled “Troubleshooting”Why does my workflow never run on a live call?
- Save & go live in the builder.
- The workflow is on for this agent (Business Workflows).
- The trigger matches the event (Call Start, On Call End or During Call).
- You called the agent that has the workflow on, not another agent.
Why does my workflow work in the builder test but not on real calls?
Builder tests run the workflow without an agent attached, so they pass even when no agent uses it. Turn the workflow on for the agent under Business Workflows, then place a real call to that agent.
