How can we help?

Components represent a specific step within an Automation Flow and are designed to perform specific tasks. 

All components have a Component Name field, which allows for a clear and concise identifier for the component within the flow, up to 40 characters in length.

Additionally, each component has a custom configuration based on its purpose within the flow. Here are the components included in an Automation Flow:

List of available components to build a flow:

• Talkdesk Event Trigger
• On-Demand Trigger (API request; Async)
• Split Flow
• Execute Action
• Get Context
• Functions
• End Flow
• Wait component (Wait For)

Talkdesk Event Trigger

This component allows setting a Talkdesk event as a flow trigger. By default, all event fields and relevant value providers are set as variables to be used in subsequent steps on the flow.

Limitations and Prerequisites

• Only 1 trigger (Talkdesk Event or On Demand) can be configured by flow. 
• Since this is a trigger component, it must be configured as the first step of a flow.

Configuration

1. Select the Talkdesk Event from the dropdown list [1].
2. All the event fields and related value providers will be listed on the component, for information only [2].
3. Click Save.

On-Demand Trigger

This component enables configuring business processes that are triggered via an API call, allowing external systems or services to initiate automation flows on demand.

Limitations and Prerequisites

• Only 1 trigger (Talkdesk Event or On Demand) can be configured by flow. 
• Since this is a trigger component, it must be configured as the first step of a flow
• API Rate limits set to 10 requests per second
• For now, this is an asynchronous process only, meaning that the flow will not handle a dedicated response; it will only return if the trigger was successful or not.
• Scopes required for the API request. Please request them directly from the Integrations Platform team.

Configuration

• Define the component name, up to 40 characters [1].
• Map the request body parameters required to start your flow and give additional context to it [2]. These will not be considered mandatory for the request.
• When configuring this request on your external system, make sure that the scopes defined in the component [3] are included in the OAuth Client configuration.
• Use the Copy Code button [4] to copy the generated code to configure the request on your external system.
• Click Save.

Split Flow

This component determines the next step to execute based on specified conditions. For each exit of the split flow component, it is possible to set multiple conditions. Note that conditions are evaluated by exit order, so the flow will decide to proceed through the first exit where conditions are met. If no conditions are met in any exit, the flow follows the fallback exit.

Applications of the split flow component:

• Configure a Split Flow before a Execute Action to apply a filter before executing an action (for example: 1 or more exits with conditions, a fallback exit directly connected with an End Flow).
• Configure a Split Flow to create different paths on the flow (for example, exit #1 leads to a “Create Task” in Salesforce; exit #2 leads to a “Create Ticket” in Zendesk).

Limitations and Prerequisites

• Split Flow allows between 1 and 10 conditional exits.
• Conditional exits allow between 1 and 10 conditions.
• Conditional exits cannot be reordered; instead, you need to delete and recreate or modify a specific conditional exit's configuration.
• All exits, including the fallback exit, must be connected to a subsequent step in the flow.

Configuration

• Define the component name, up to 40 characters [1].
• Define as many exits as you require [2]. Each exit will connect to a different path in the flow [3], including the mandatory fallback exit.
• When defining an exit:
  • It is possible to add 1 or more conditions to an exit [4]. 
  • It is possible to define if all or any conditions should be matched (and/or) [5].
  • It is possible to use values or variables from previous steps [6].
• Click Save.

Execute Action

This component allows you to execute an integration action as a step within the flow. Similar to Automations, it requires mapping the fields that should be sent with the action. Users can select these fields from a list of available variables (defined in previous steps) or assign specific values manually. If the action has defined outputs, these will be automatically exposed as variables and made available to use in subsequent steps.

Limitations and Prerequisites

• Currently, only Connections actions are supported.
• Only actions from installed and active integrations are listed.

Configuration

1. Define the component name, up to 40 characters [1]
2. Select the Connection and the respective action [2]
3. If the action has inputs, then map variables/values for each input of the action [3]. Only variables defined on previous steps can be mapped.
4. If the action has outputs, the outputs will be automatically defined as variables to be used on the following steps [4]
5. Click Save

End Flow

The End Flow component sets the end of the flow. All flow paths must end with an End Flow component.

Limitations and Prerequisites

• Only 1 End Flow component can be configured per flow, so all paths must be connected to the same End Flow component.

Configuration

1. Define the component name, up to 40 characters [1].
2. Click Save.

Get Context

This component allows you to fetch context variables defined in Studio and use them as flow variables. This step is mandatory if you want to use context information in a flow.

Limitations and Prerequisites

• Only context from the interaction is available at this time, and it will only work if you receive the interaction ID on the flow.
• Context must be available to “Conversations & Automations” on Studio configurations. Follow this documentation to learn how to manage context.

Configuration

1. Define the component name, up to 40 characters [1].
2. Map the variable that returns the Interaction ID [2]. If the TD Event selected on the trigger has by default that information, the variable will be listed by default on the variables dropdown.
3. Map the context fields required for your flow. On the variable name [3], write the context variable name as it was defined in Studio. In this example, we are mapping the context field “url_test” (from column “Variable”).

4. To map more fields, select the button “Add field” [4].
5. To delete a variable, use the bin button displayed in front of each mapped field [5].
6. Click Save [6].

Note: Regarding duplicated fields, when configuring the Get Context component, if a duplicated field is configured (i.e., a variable with a duplicated field name), and the user clicks Save, all the configurations will be saved with the exception of the duplicated field. A toast message will be displayed, specifying that the duplicated field was not saved.

Functions

This component allows executing JavaScript functions for data transformation. 

Configuration

1. Define the component name, up to 40 characters [1].
2. Define a variable or value (string) for each parameter that you want to include in the function [2]. Use the “Add input” action [3] to configure all the required inputs.
3. Define at least 1 output parameter for this function to return (mandatory) [4]. It is only required to define the name. Use the “Add output” action [5] to configure all the expected outputs. These outputs will be automatically mapped as flow variables.
4. Define your JavaScript function using the inputs and outputs defined in the previous steps [6]
5. Click Save [7].

Wait Component (Wait For)

This component allows you to pause a flow before continuing to the next step.

Limitations and Prerequisites

• The flow can be paused for up to 30 days
• This component includes a single exit for success

Configuration

1. Define the component name, up to 40 characters [1].
2. Define how long the flow should pause. Use the dropdown to define the time unit [2].
3. Click Save [3].