Videos: Building agentic workflows

Examples on how to build agentic workflows in watsonx Orchestrate.

Building an agentic workflow with user activities

Here is an example of how to build an agentic workflow that uses user activities:


In this example, you are creating an agentic workflow, previously known as flow, that uses user activities to add a hiring employee. A user is guided through entering details for a new hire, including: employee name (string), employee number (integer), role (list), availability (boolean), and start date (date). These inputs are configured as user activities. The agentic workflow uses a branching condition to assess availability and concludes with a summary message generated by using a code block. This example also illustrates how configured prompts appear in the chat interface. To learn more about creating an agentic workflow, see Creating agentic workflows.

Building an agentic workflow with generative prompts

In this example you are creating an agentic workflow, previously known as flow, that uses generative prompts to get a car quote. A user is guided through selecting the specifications of a car, including: select brand (single choice), select model (single choice), registration date (date), and whether to proceed with the quote (boolean). These inputs are configured as user activities. The agentic workflow uses branching condition to determine whether to proceed with the quote concludes with a summary message which is generated by using code block and generative prompt. This example also illustrates how configured prompts appear in the chat interface. To learn more about creating generative prompts, see Adding generative prompts.

Building an agentic workflow with forms

In this example you are creating an agentic workflow, previously known as flow, that uses forms to book a flight. A user is guided through a series of questions to provide travel details, including: departure city (single choice), arrival city (single choice), trip type (single choice), departure date (date), arrival date (date), ticket class (single choice), and number of travellers (number) and whether to proceed with booking (boolean). These inputs are configured as user activities. The agentic workflow then analyzes the inputs and suggests an available flight list, allowing the user to choose a flight. It uses a branching condition to determine whether to proceed with the booking and concludes with a summary message generated using code blocks. This example also illustrates how configured prompts appear in the chat interface. To learn more about creating forms, see Forms in user activities.