Skip to main content
This page lists every trigger and step in the workflow editor, with the names the editor shows. Use it to find the right trigger for an event, or to check whether a step needs an integration, a channel or a setting before you build with it.
The editor lists these under TRIGGERS, ACTIONS and BLOCKS when you click + in Agentic Workflows. Once a workflow has a trigger, the editor only offers the steps that work with it.
Some names use the word “ticket” (Ticket Created, Tag Ticket). They act on OpenCX sessions. Inputs named Ticket Number take the session number.

Triggers

Each workflow has one trigger. Its data is available to every step as {{trigger.…}}; see variables. Most session triggers also accept Channels, Directions and Statuses filters and a Run Synchronously option, set on the trigger in the editor.

Session triggers

Message and AI triggers

Manual, macro and CSAT triggers

Run a workflow from a session. Active Manual Ticket Trigger workflows appear in the Run Workflow card in the session sidebar of the inbox. The agent picks one and clicks Run workflow; the workflow’s description is shown in the dialog. To ask the agent for details first, add fields to the trigger’s Form Schema: the dialog shows them as a form, and the answers reach the workflow as {{trigger.formData.<field>}}. Running needs Workflows (Write), Run workflows (Write), or Assigned sessions (Write) on a session the agent can see. Run a workflow from a macro. Pick the macro in the Macro Called trigger, or link the workflow from the macro’s Workflows field in Settings → Macros. See CSAT for collecting the ratings that CSAT Score Submit reacts to.

Schedule, webhook and form triggers

After you activate a Webhook or Form Submit workflow, click Guide at the top of the editor. For a webhook it shows the Trigger URL, its access level and a curl example; the URL stays the same across versions. With Access Control set to Private (Authentication Required), callers send an API key with the Trigger and invoke workflows scope, created in Settings → API Tokens. Public (No Authentication) lets anyone with the URL run the workflow. For a form, the guide shows the Form ID and example requests.

Contact, agent, SLA, phone and sequence triggers

The sequence triggers can each be narrowed to specific sequences.

Steps

Blocks and flow

Session status, assignment and routing

Replies, notes and outbound messages

AI steps

Set Expected Output on the AI steps to get named fields back, for example {{ask_ai.result.category}}.

Sessions, contacts and companies data

Documents, web and text

Slack

Sequences and outbound blocklist

Phone and Classical IVR

Integration steps

Run Code

Run Code runs a JavaScript snippet. The Code field starts as return {}: whatever you return becomes the step’s Result, which later steps read as {{run_code.result}}. Inside the code, the trigger and earlier steps’ data are on $ctx, and the editor autocompletes its fields. Code can’t import modules or use eval. A run fails if the code throws or doesn’t finish in time.

Steps that need an integration, channel or setting


Build a workflow

Canvas, conditions, variables.

Test and monitor

Test runs and failure states.

Workflows overview

Use cases, life cycle, permissions.

Workflows API

Create and trigger workflows by API.