Actions

overview actions are a powerful category of elements in the flow builder that serve as the "engine" of your chatbot's logic unlike bot messages or prompts, which are user facing, actions work behind the scenes to perform operations, manipulate data, control the conversation's path, and integrate with external systems they are the crucial link between the conversational interface and your business processes think of actions as the verbs of your chatbot; they are responsible for doing things whether you need to fetch a user's order details from your e commerce platform, save new lead information to a database, or hand off a complex query to a human agent, you will use an action element the available action types include flow control execute flow, switch flow, and delay manage the user's journey through different conversational paths external integrations api and transfer to live chat connect your chatbot to other software and services data management database, function, variables, and modify data allow you to retrieve, store, and manipulate information within the conversation using these elements effectively is key to building a chatbot that is not just conversational, but genuinely functional and helpful how to use actions actions are added as elements inside a node on the flow builder canvas 2 1 adding an action on the flow builder canvas, click the + icon on a node or the add more button inside a node from the element menu, select the actions category choose the specific action you want to perform (e g , api, database) 2 2 configuration details for each action type execute flow & switch flow these actions control the user's navigation between different flows execute flow temporarily runs another flow (a "sub flow") and then returns to the next step in the original flow once the sub flow is complete this is useful for reusable tasks like collecting an address switch flow permanently redirects the user to a different flow, ending the current one configuration for both, simply select the target flow from the dropdown list of all flows in your bot api this action calls an external api that you have pre configured in the api module select api choose the desired api call from the dropdown list map variables if the api requires input (e g , a user id), map the flow variables containing that data to the api's expected input fields store response select a variable where the api's response data will be stored connect paths the api element creates two output connectors success and failure you must connect both to subsequent nodes to handle both possible outcomes database this action allows you to interact with a table you have created in the database module select table choose the target database table from the dropdown select action choose the operation to perform insert entry, update entry, search entry, or delete entry map columns map your flow variables to the corresponding columns in the table for the operation for example, for an insert entry action, you would map the {user email} variable to the "email" column transfer to live chat this action initiates a handoff to a human agent enter message text configure the message the user will see while they wait to be connected (e g , "please wait while i connect you to an agent ") map user details select the variables that hold the user's name, phone number, and email this information will be passed to the live chat system to give the agent context delay this action pauses the conversation for a set period, which can make the bot feel more natural enter delay specify the duration as a number select units choose whether the duration is in second(s), minute(s), or hour(s) function, variables, and modify data these actions are for advanced data handling within the flow function execute a custom python script (pre configured in the functions module) to perform complex logic variables explicitly set or change the value of a variable modify data apply built in data transformations to a variable (e g , convert text to uppercase, perform calculations) common use cases checking an order status (api) a user provides their order number, which is stored in a variable an api action sends this variable to your logistics system and stores the response (e g , "in transit") in another variable, which is then displayed to the user saving a sales lead (database) after a user fills out a contact form, an insert entry database action saves their name, email, and query into a "leads" table handling escalations (transfer to live chat) if an api call to resolve a user's issue fails, the failure path can lead directly to a transfer to live chat action to connect them with a human agent modular user authentication (execute flow) create a single, reusable flow for user login from other flows (like "check account balance" or "update profile"), use execute flow to run the login flow once the user is authenticated, the conversation returns to the original flow best practices handle every outcome always connect the success and failure paths for actions like api and database a user should never be left at a dead end if an integration fails use execute flow for reusability identify common tasks (like asking for an email or authenticating a user) and build them as separate, small flows call them with execute flow to keep your main flows clean and easy to manage provide feedback to the user before a potentially slow action like an api call, use a text message to inform the user (e g , "let me check that for you ") keep sensitive data out of variables avoid storing highly sensitive information like passwords or full credit card numbers in variables for extended periods process and discard them as quickly as possible common mistakes confusing execute flow and switch flow using switch flow when you intend to return to the original flow is a common error that prematurely ends the user's journey use execute flow for temporary tasks not storing api responses calling an api but forgetting to configure a variable to store the response means you can't use the data you just fetched incorrect variable mapping sending the wrong variable or incorrectly formatted data to an api or database action will cause it to fail double check your mappings