Important Note: This feature is available in Preview for select customers.
Automation Flows is a no/low-code orchestrator that enables Admins to automate advanced use cases that can touch multiple integrations. Automation Flows allows building multistep and multi-integration business processes that can be triggered by Talkdesk Events or evoked via API. With an intuitive designer, Admins will be able to build flows that can connect to multiple external systems and define more complex processes.
Understand what Automation Flows supports, what it does not support, and current limitations in this article.
Core Concepts
New type of flow - Automation Flow
An Automation Flow is a new type of flow for creating business processes that integrate with external systems (for example, creating a ticket in a CRM) or internal Talkdesk products (for example, invoking an AI Agent).
It supports multistep, multi-integration processes, allowing you to define conditional paths and execute actions across multiple connected systems — a single flow can handle integrations with different systems.
Note: Currently, only Connections actions are supported. Other integrations’ actions are planned for the near future.
Automation Flows List
Within the Automation Flows list (accessible from Builder > Automation Flows), you can create, edit, and view the existing Automation Flows. The Automation Flows list provides information about the flows, including:
- Name
- Version state: Can be Draft or Published. Only published flows are able to execute.
- Last published date
- Status toggle: Switch between Enable and Disable. Please note that only published flows can be enabled.
Creating or editing a flow from this view will automatically redirect you to Automation Designer.
Components
Components represent a step within a flow. Each component defines a specific action, collectively determining the flow's functionality. For more details, check the list of available flow components here.
Variables
Variables store and pass data between steps in a flow. By default, all component outputs (such as event fields or action results) are automatically set as variables. You can also use custom variables (user-defined) and system variables (predefined, read-only).
Automation Flows follow a step variables model: when configuring a component, you can only map variables created in previous steps of the flow. This ensures data moves forward in execution order and avoids circular references.
Additionally, with the Get Context component, it is possible to bring Studio Context variables to be used in a flow.