Skip to content

Task 2 - Build Autonomous Webex AI Agent Actions

Please use the following credentials to connect to Control Hub and configure Webex Contact Center:

Control Hub URL https://admin.webex.com
Username labuserID@wx1.wbx.ai (where ID is your assigned pod number; this ID will be provided by your proctor)
Password webexONE1!

Objective

In this lab, audience will learn to explore and set up Autonomous Webex AI Agent actions using Webex Connect flows. They will also learn how to configure these flows to interact with external APIs, allowing the AI Agent to handle data and fulfill requests by connecting to other services.

Section 1 : Create a Webex Connect Flow for Car Order

  • Action fulfillment for the agent is always handled via Webex Connect flows.

  • Lets begin by creating a Webex Connect flow, which can later be selected to a specific Webex AI action.

  • Navigate to the Webex Connect portal through the 'Quick Links' section in the Webex Contact Center area of Control Hub.

Nav

  • Create a new service by clicking 'Create New Service' and providing a name Webexone_carorderservice_YourName_.

Nav

  • Navigate to 'Flows' section and click 'Create Flow'.

Nav

  • Provide a 'Flow Name' (i.e. carcreateorder_name), ensure that 'Start from Scrach' is selected, and click 'Create'.

Info

This flow will interact with external database using API to create a car order.

Nav

  • In the next menu, select 'AI Agent' under 'Integrations'.

Nav

  • 'Configure AI Agent Event' is displayed. Under 'Provide sample Json' provide the variables that will be passed from the Webex AI Agent. For a new car order, use the following:
    {
    "model": "",
    "color": "",
    "engine": "",
    "customer": ""
    }
    
  • Click 'Parse' and 'Save'.

Nav

  • Drag the 'HTTP Request' node from the left-hand side menu, place it next to the 'AI Agent' node, and connect them by clicking and holding the green dot on the 'AI Agent' node and dragging it to the 'HTTP Request' node.

Nav

  • Double click on the 'HTTP Request' node and fill the fields as follows:
Field name Value
Method PUT
Endpoint URL https://68085a3f942707d722ddf6a8.mockapi.io/api/cars
Header Content-Type
Value application/json
Output Variable Name (click '+Add Variable') orderid
Response Entity Body
Response Path $.orderid

For 'Body' section use:

{
 "color": "$(n2.aiAgent.color)",
 "engine": "$(n2.aiAgent.engine)",
 "model": "$(n2.aiAgent.model)",
 "customer": "$(n2.aiAgent.customer)"
}

  • Click 'Save'.

Nav

  • Configure 'HTTP Request' node outcomes by dragging the orange, green, and red outcome dots to empty space on the canvas and selecting appropriate outcomes (e.g., 'onTimeout' - Error, 'onSuccess' - Success, 'onError' - Error).

Nav Nav Nav

  • Next, click 'Flow Settings' (gear icon), navigate to 'Flow Outcomes', and expand 'Last Execution Status' outcome.
  • Click 'Add New', use 'orderid' under 'Key' and '$(n3.orderid)' under 'Value'.
  • Click 'Save'.

Nav

  • Make the flow live by clicking 'Make Live' (top right corner) and then clicking 'Make Live' again in the next dialog box.

Nav

Section 2 - Configure AI Agent Car Order Action

  • Navigate back to the AI Agent Studio and to your Autonomous Webex AI Agent.

  • Select 'Actions' and click 'New Action'.

Nav

  • Provide an 'Action Name' (use carordercreate).
  • Provide the following 'Action description':
    Submit a car order when the customer chooses a model and all other customization options.  
    Provide orderid after a successful order.  
    
  • Under 'Action scope', select 'Slot filling and fulfillment'.

Nav

  • Select the service you created in the previous task under 'Select service' and the flow created above under 'Select a flow'.

Nav

  • Click 'New input entity'.

Nav

  • Add four entities for the Webex AI Agent to pass to the Webex Connect flow with the following parameters:
Entity name Entity type Entity description Entity examples Required
model String Car model that the customer chose NovaTerra Yes
color String Car color that the customer chose Ruby Red Yes
engine String Engine type that the customer chose gas, electric Yes
customer String Customer's name Jack, Nick Yes

Nav Nav

  • Click 'Add' and Publish the changes.

Nav

Section 3 - Test Webex AI Agent

  • Let's test the logic by creating a new car order by going back to AI Agent Studio and selecting the Autonomous AI Agent created in exercise 1.

  • Click 'Preview' and Verify the functionality by creating a car order.

Nav

  • For guidance the screenshot provides an example of how an order is created.
    • First, the user expressed the intent to buy a new car.
    • As per its instructions, the AI agent requested car details like the model, engine type, and color.
    • When a detail was missed, the agent was able to ask the user to provide the missing parameter to complete the order.
    • Once it received all the necessary information, it successfully created the order and provided the order details.

Nav

  • In your case, you will see that the agent is not able to provide the order ID. Specifically asking the agent for the order ID was not helpful either.

Nav

  • To begin, verify the session details to confirm the agent's actions by going into the Agent and Sessions Section.

Nav

  • Choose the latest Session ID.

  • Note that the fulfillment was successful, and information was provided to the Connect Flow for order execution.

Nav

  • Next, lets examine the Connect Flow debugs to see how the information was executed.

  • To access these, navigate to Control Hub > Contact Center Quick Links > Webex Connect, and then select the Connect service you created.

Nav

  • Within the service, select your created Flow and click the Debug option on the right side. The Transaction Logs window will open.

Nav

  • First, click Decrypt Logs to convert the logs into text, then select the latest transaction.

Nav

  • You will see three nodes being executed.

  • The "Configure AI Agent Event" payload is constructed and passed to the "HTTP Request Node."

Nav

  • In the HTTP Request Node, you'll see the request data was constructed and the API was executed. However, the response data shows a status of 400 Bad Request, indicating the request was not processed due to an invalid request.

Nav

  • The issue lies in the method selected to create the record. PUT is generally used for updating or replacing existing content, but for creating a new record, the correct method is POST.

  • To correct this, select the Edit option in the flow. Then double click on the HTTP Request Node and change the Method from PUT to POST.

Nav

  • Save the flow and make it Live.

  • Create a car order again from Preview chat, and the execution should now be successful with AI agent returning an Order ID.

Nav

  • You can also access the datastore where these orders are stored and updated by entering the following URL into your browser:

Car Orders

Nav

Congratulations! - You have successfully completed this task and the lab! If you'd like, you can also explore Bonus excercise 5 to dive and see how the orders can be modified.