Skip to main content
OpenCX workflows act on Genesys Cloud sessions too: the usual actions reach the Genesys conversation, and a few actions are Genesys’s own. Read this when you build a workflow, or an AI-trigger workflow the AI can call, for a Genesys workspace. To import one past Genesys conversation in a workflow, see Import past conversations.

Callbacks

Create Genesys Callback asks Genesys to call the customer back from a queue, now or at a set time. The callback carries the session’s summary and its link as opencx_summary, opencx_inbox_url and opencx_session_id, an internal note on the session records it, and the session keeps the callback’s conversation ID as genesys_callback_conversation_id. With every Genesys conversation shown, the call appears as a sub-session of that session. A number not in international format, a time in the past or a queue that isn’t synced is refused before anything reaches Genesys. If Genesys refuses the callback, the step fails, and Health asks you to reconnect when the permission is missing. To let the AI book callbacks, create an AI-trigger workflow, for example “Book a callback when the customer gives a phone number”, with a phone number in its payload and the Create Genesys Callback action using the session ID and that number. Offer a callback under When no agents are available uses that workflow.

Data Actions and data tables

The Data Actions and data tables your Genesys flows already use work in OpenCX workflows too, so the AI can look up an order, a balance or a delivery zone the same way your IVR does.
  • Run Genesys Data Action: pick the action from your Genesys org (listed as name · category), then fill in its inputs, typed or mapped from earlier steps, named exactly as in the action’s input contract (in Genesys: Admin › Integrations › Actions, the action, Setup › Contracts). Inputs that don’t match the action’s input contract stop the step before the action runs. Later steps use the fields of Output. Secure Data Actions aren’t listed or run, so data Genesys keeps secure stays in Genesys. An action that fails or takes longer than 30 seconds fails the step and is never run a second time.
  • Lookup Genesys Data Table Row: pick the table (the list shows its key column), then give the key. Found is false when the table has no row with that key, so a later step can branch on it.
The queue, Data Action and data table lists show only what your own Genesys org has, and stay empty until Genesys is connected. Instead of picking, any of them can take a variable from an earlier step. To let the AI use them, add them to an AI-trigger workflow, for example “Check the customer’s balance when they ask for it”, with what the action needs in its payload. The AI gets the workflow’s result. Both work only once your organization is on Genesys, and only with actions and tables in your own Genesys org. They need integrations:action:view and integrations:action:execute for Data Actions, and architect:datatable:view for data tables. When Genesys refuses one a workflow runs, the step fails and Health asks you to reconnect Genesys to grant it.

Handoff settings

Offer a callback when nobody is on the queue.

Permissions

Callbacks, Data Actions and data tables need their own permissions.