Skip to main content
An Agentic Workflow is a trigger plus a chain of steps that OpenCX runs on your sessions: when something happens (a session is created, a customer goes quiet, an SLA is breached), the steps run in order. Use workflows for the work that should happen the same way every time, without an agent or the AI deciding to do it.
Agentic Workflows in the main sidebar of your OpenCX dashboard. Viewing needs the Workflows permission (Read); building and activating needs Workflows (Write).
Ready to build? Go to Build a workflow.

How a workflow is put together

Every time the trigger fires, OpenCX starts a run. Runs are listed in the workflow’s Runs tab with each step’s input, output and errors. See Test and monitor workflows. Some trigger and step names use the word “ticket” (for example Tag Ticket). They act on OpenCX sessions.

What teams use workflows for

Trigger: Ticket Handed Off. Steps: Auto Assign to Support Team picks a team from the session summary, then Tag Ticket labels the session. Add an If Block on the sentiment to send angry customers to a priority team with Assign Ticket to Support Team instead.
Trigger: Customer Inactive (for example, inactive for 24 hours after an agent reply). Steps: Reply to ticket with a check-in message, Wait two days, Get Session By Ticket to read the current status, then an If Block that runs Close Ticket only if the session is still open.
Trigger: SLA First Reply Breached. Steps: Send Message to a Slack Channel with the session number and team, then Apply SLA or Change Ticket Assignee to escalate.
Trigger: AI Trigger. The AI calls the workflow mid-session when the customer’s request matches The Goal of the Workflow. Steps: Make HTTP request to your order system, an If Block on the response, then Merge Custom Data to save the result on the session.
Trigger: Manual Ticket Trigger. Agents run it from the Run Workflow card on a session, optionally filling a short form first. Steps: Create Zendesk Ticket from Session, then Append note with the Ticket URL it returns.
The full list of triggers and steps, and which need a specific integration or channel, is in Triggers and steps.

Workflows, AI Actions and Autopilot

Workflows work alongside Autopilot rather than replacing it. Steps such as Set Conversation Mode (switch a session between Autopilot and Assist mode), Assign Ticket to AI, Unassign AI and Respond with AI change how the AI handles a single session. The AI Response Requested trigger only fires when the AI would actually reply, so it never fires on handed-off sessions or where Autopilot is off. AI phone agents use the workflows linked to them in the phone agent editor, not the Channels filter on the AI Trigger.

Workflow life cycle

The workflow list shows each workflow as Active or Draft, grouped by trigger. Editing an active workflow never changes what’s running: your edits go to your draft, and the active version keeps running until you save a new version and activate it. Version history keeps every saved version, so you can switch back to an older one by activating it. See Build a workflow.

Who can use workflows

Permissions are set per role in Settings → Roles. See the permissions reference.

Build a workflow

Canvas, conditions, variables, versions.

Triggers and steps

Every trigger and step, with requirements.

Test and monitor

Test runs, the Runs tab, failures.

AI Actions

Single API calls the AI makes.