Actions
Actions define specific tasks that an agent must perform as part of its goal-driven workflow. Their primary purpose is to guide the collection of required data by specifying what information is needed, in which order it should be obtained, and whether each piece of data is mandatory.
Based on this definition, the agent gathers the input in the most appropriate way and then activates a action. The action uses the collected data to execute a specific function—such as summarizing information, generating content or reports, or automating workflows.
Within the dialogue flow, actions act as the data collection mechanism, while the flow itself uses that data to carry out the intended operation in real time.
The name and Instruction fields are critical steps that will determine how to process and execute the action.
New Action
Fill the presented fields:
Name: It should be clear and descriptive of the task the action will perform. Use lowercase letters and separate words with underscore (e.g., search_flight, destination_recommender).
Instructions: This field provides detailed information about what the action does, its purpose, and when it should be triggered, which makes it essential for its correct functioning. For the action search_flight, for instance, the description is “Trigeer this action when users request to book a flight, buy a ticket, reserve a trip, or similar actions, execute them accordingly.”
Parameters
Once you've defined what it should do, now specify how. Breakdown which data should be collected by using the Parameters block. Start by choosing between two approaches: Basic and Advanced.
In advanced mode, you can use a JSON containing all the parameters required for the success of this action for more technical and precise action definition.
Here is a JSON example for Advanced Mode:
Whereas in basic mode, you can add the parameters individually for easier configuration.
Fill the presented fields:
Parameter Name
Type: Defines the data format (string, boolean, number) that the parameter accepts
Parameter Description: Explains the purpose and expected values for this specific parameter
Variable (optional): Assigns a reference name that can be used elsewhere in the agent's workflow. The value can be accessed through $hiddenContext.variable, such as: $hiddenContext.numberOfPassengers (see table).
Rules (optional): Specifies constraints, validations, or conditional behaviors that govern how the parameter works. They serve as tactical directives.
For the action search_flight above mentioned, there are five parameters: date, origin, destination, type of flight, number of passengers. Here's a more detailed breakdown for two of them:
Name
numberOfPassengers
dates
Type
String
String
Description
The number of passengers traveling, including both adults and children. The passengers must be adults.
The dates of travel, including departure and optionally return, provided in a format like YYYY-MM-DD or DD/MM/YY. The date provided is a valid date, i.e. it must be a future date, The departure and destination dates must correspond to a valid period. The current year is 2025.
Variable
numberpassengers
--
Rules
- If you are informed that they are a children or student, kindly recommend that they book the flight online: website.com/buy-tickets
- The number of passengers must be 9 people max. If there are more than 9 people, kindly recommend that they book the flight online: website.com
If the user gives you a round-trip date, assume it is a 'round-trip flight'
These fields collectively form the framework that enables an agent to properly understand, process, and respond to user inputs while executing the specific tasks needed to achieve its goals.
Tools
If you need to execute an API call, add a Service cell right after after the desired action in the workflow. It can be a Webhook or a Rest Connector cell, mechanisms that transforms the Action's intent into concrete API interactions, allowing the agent to retrieve or manipulate data needed to fulfill its purpose.
In the example, a Rest cell was chosen to perform an API call. At a visual level, you’ll see the Agent cell and the branches for each Action added and for error handling. In this case, itinerary_option and destination_recommender, and the button error.
Action templates
Examples of actions to speed up your agent creation process. Adapt and change according to your business cases.
After the branch for the formatting actions, add an answer cell with the variable registered in the parameters.
Last updated
Was this helpful?