Skip to main content
The call ends. Now what? The lead booked, or asked for a callback, or said never again. Each of those should do something different in the CRM. A campaign workflow is that mapping: for each outcome, a list of actions the platform runs the moment the call is over. You do not have to build one. A campaign works without a workflow and still applies the automatic tags. Build one when “tag it” is not enough.

​
Outcomes are the entry points

The workflow is a graph with one root per outcome. The keys under dispositionEntries are the outcome constants: An outcome with no entry does nothing beyond the automatic tag. The outcomes a campaign can actually produce depend on its capabilities. See What your agent records.

​
Nodes and edges

nodes is an object keyed by node id. Each node has a type and its own settings. edges[] connect them with source, target and, on branching nodes, a sourceHandle naming which exit the edge leaves from. Conditions on if and switch compare an AI-generated field or a contact field with an operator: is_true, is_false, is_set, is_empty, equals, not_equals, contains, starts_with, in, gt, gte, lt, lte.

​
Campaign-wide settings

campaignConfig on the same document holds settings that shape every branch:
  • callbackMode: ai lets the agent place callbacks, human routes them to your team, with humanCallbackCalendarId naming where to book them.
  • aiNotes and noteLanguage: whether the agent writes a call note and in which language.
  • convertedTag: the tag that marks a lead as converted.

​
Saving without breaking a live campaign

The workflow runs on real calls while you edit it, so the write endpoints are built to fail loudly rather than lose a branch.
  • Every read returns version. Send it back as expectedVersion on a write. If someone saved in between, you get 409 and reload.
  • The replace endpoint swaps the whole graph. If the new graph drops nodes, you must send allowRemovals: true, and a 400 lists what would go.
  • The update endpoint merges. It changes settings and the contents of nodes that already exist. It never creates a node.
  • The add actions endpoint appends nodes to one outcome’s branch in a single step, so a partially applied chain cannot exist.
  • The remove node endpoint deletes one node and its edges.

​
Advisories

Reads return advisories[], checks that do not block saving but tell you where the graph is weak: The digest endpoint gives the same graph as one line per outcome, which is the easiest way to review what a campaign will do.

​
Boundaries

  • One workflow per campaign. Campaigns on the same agent share the agent but not the graph.
  • Branches run after the call. They cannot change what the agent says.
  • Automatic tags are applied whether or not a workflow exists.
  • A 409 means reload, do not retry blindly.

​
In the API