Action

The Action section defines what the system must do after the procedure’s goal is met. This ensures that specific tasks, such as inputting data into a database or triggering other processes, are automatically executed once all conditions are fulfilled.

---

Prerequisites

To effectively configure Actions within the system, it’s essential to understand how the Tools - API Call feature operates. Familiarizing yourself with API Calls will ensure a smooth setup and accurate data handling in your automated workflows.

👉 Learn more about setting up API Calls here

API - Call

Logic

Action Logic - How it works

• Triggering the API Call: Once all required complaint information is collected and the goal is achieved, the system sends an API request to submit the complaint to the specified endpoint. This can include adding details like the complaint description and the user’s contact information.

• Automation: The API Call establishes an automated connection between the complaint procedure and external systems, ensuring complaint data flows seamlessly without needing manual input.

• Action Execution: After the goal is completed, the SubmitComplaintTicket action is triggered, sending all complaint details to the external system for processing.

Adding New Action

How to Configure

1. Add Action

   • Click the + Add Action button under the Actions section.

   

   Add Action

   • From the dropdown, select API Call to create a new API call action.

   

   Add Action API Call

2. Configure the API Call:

   • For detailed guidance on setting up an API Call, please refer to the API Call Configuration Guide below.

API - Call

Notes to Configure:

1. Enable the Toggle: Turn the toggle on to activate the Body Field.

2. Select Binding Type:

   • Input Binding: Use when sending data to an API (e.g., submitting a form or creating a resource).

   • Output Binding: Use when expecting to retrieve data from an API (e.g., getting transaction details).

   • Both Input and Output Binding: Use when you need to send data and get a response that will be mapped in the system (e.g., submitting a claim and receiving a confirmation).

---

Action Section

Purpose

The Action section enables the AI to perform specific tasks, such as inputting data or executing an external process, once the procedure’s goal is achieved. This ensures that the collected data is handled appropriately within the system, such as storing claim information in the appropriate database.

How to Configure:

1. Add Action:

   • Click the + Add Action button in the Actions section to define a new action.

2. Select Action:

   • From the dropdown menu, choose the action that will be triggered once the goal is met. This could involve sending data, updating records, or initiating external workflows.

     

     Apply API Call Action to Goal

Apply to Goal:

• After selecting the action, click Apply to Goal to link it to the procedure’s goal. This ensures the action is automatically executed when the goal is fulfilled.

Configured Action