Skip to main content
An automation connects Callivox to the other tools your business runs on. It watches for something happening — a message arrives, a form is submitted, a schedule comes round — and then does work for you: create a CRM record, update a spreadsheet, send a message, place a call.

The Automations page lists your flows, grouped into folders, with their status and when they last ran.

Where to find it

Open Automations in the left sidebar. The page header reads Automations, with a Connections button on the right and two tabs: Flows and Runs. Automations are part of the Integrations & automations feature, so availability depends on your plan. The builder needs a drag-and-drop canvas, so it is desktop only — on a phone or tablet you will see a notice reading “Editing an automation needs the drag-and-drop canvas — open Callivox on a larger screen to build or edit one.”

The parts of a flow

A flow is a diagram you build on a canvas. It has two kinds of pieces:

A trigger

Exactly one, and it always comes first. The trigger decides when the flow starts — a Callivox event, an incoming webhook, a schedule, or something happening in a connected app.

Actions and logic

Everything after the trigger. Actions do the work (create a contact, send a message, add a row); logic blocks branch, loop and transform data along the way.
You connect the blocks by dragging a line from one block’s output to the next block’s input. That line is the order the steps run in. An automation can only have one trigger. If you try to drop a second one, Callivox shows “An automation can only have one trigger.” — delete the current trigger first.

Flows and runs

The two tabs on the Automations page answer two different questions. See Runs and troubleshooting for how to read a run.

Status: draft, published, off

Each flow row carries one status badge: Save keeps your edits without changing what is live. Publish makes the version you are looking at the one that runs. Saving never un-publishes a flow that is already live.

Turning a flow on and off

Use the menu on a flow row and choose Disable (or Enable to switch it back on). Disabling is the way to pause an automation without losing it — the flow, its settings and its run history all stay exactly as they are, and re-enabling arms the trigger again.

Organising flows into folders

Flows group into collapsible folder sections. Anything you have not filed sits under Uncategorized.
  • New folder on the toolbar creates one.
  • Move to folder… in a flow’s menu files a flow.
  • A folder’s own menu offers Rename and Delete. Deleting a folder does not delete its flows — they move to Uncategorized.

Deleting a flow

Delete is in the flow’s menu, and you will be asked to confirm. If the flow is still live, the confirmation warns: “This automation is still enabled — deleting it stops it from running immediately, and this can’t be undone.”
Deleting a flow does not erase its history. Past runs stay visible under Runs.

Automation runs and your plan

Every plan includes a number of automation runs per billing period. A banner at the top of the Automations page tracks where you are — for example “820 of 1,000 runs remaining”, plus any overage for the period. When the allowance is used up, the banner changes to “Automation runs exhausted” with the text “You’ve used all 1,000 included runs. Upgrade your plan to keep running automations.” and an Upgrade button. At that point Save and Publish are paused too, not only running — the builder shows “You’ve used all your included automation runs this period — saving and publishing are paused until you upgrade your plan.” If your workspace is billed by an account manager, the banner points you to them instead of showing an Upgrade button. See Running low and running out for what else is affected when an allowance runs dry.

Next steps

Building a flow

A walkthrough of the canvas, the palette, passing data between steps and publishing.

Triggers

Every way a flow can start, including webhooks and schedules.

Connectors and connections

The apps you can connect, and how to authorise them.

Runs and troubleshooting

Reading a run, finding the failing step and fixing it.