# Workflows Workflows are **conversational paths that define how the chatbot responds to specific questions and manages various scenarios**. They are used to validate user responses, determine how to reply, and define conditions that trigger different responses based on user input, among other things. Workflows are **structured processes that guide how the virtual assistant interacts with users**. Before an agent responds or the assistant takes action, the workflow ensures all necessary steps are followed. These steps are designed to react to both direct (explicit) and indirect (implicit) user inputs. Workflows represent a **step-by-step process that must be completed before an agent responds or the virtual assistant takes action**. While it's mandatory to configure at least one agent, workflows are **optional** and can be implemented as needed. For simple setups, you can build a virtual assistant composed solely of agents. However, for more complex scenarios, workflows become essential. For example: * **Product Recommendation** Workflow: User requests the best product → virtual assistant retrieves and filters options from the catalog → best-fit product is passed to the agent → agent shares the recommendation. * **Customer Support** Workflow: User asks to connect with a human → workflow gathers conversation history and user details → virtual assistant connects with the CRM → support ticket is created and confirmed to the user. ### Building a workflow Workflows are the backbone of complex virtual assistants, but building them is simple. In your workspace, you can easily **drag and drop** workflow components from the available **blocks**, making workflow creation both intuitive and flexible.

The Workflow Area and Its Building Blocks

{% hint style="info" %} Find detailed information about workflow building blocks here: [Blocks](/getting-started/agents-workflows-and-triggers/blocks.md) {% endhint %} ## 🎯 Workflow Trigger The workflow trigger functions similarly to an agent trigger, determining **when the workflow should begin (entry point)**. This ensures smooth integration with other parts of your bot. As mentioned in [Agents, Workflows & Triggers](/getting-started/agents-workflows-and-triggers.md), a trigger should only be configured if the workflow is a primary process that the mother agent should delegate user requests to. For secondary workflows or those supporting other processes, triggers are unnecessary; these workflows can be activated in an alternative way, using a [reroute block](/getting-started/agents-workflows-and-triggers/blocks/logic-blocks/reroute-block.md). {% hint style="info" %} For detailed guidance on creating workflows and building your virtual assistant, refer to this article: [Build Your AI Agents](/build-your-ai-agents/define-your-virtual-assistants-objectives-and-design-the-conversational-flows.md). {% endhint %} **What You Can Specify in the Trigger:** * **Trigger Details** – Define when the workflow should activate. * **Example Questions** – List common user queries that should trigger this workflow, helping refine its activation conditions. Additionally, there is a toggle switch that allows you to **enable or disable the trigger**. This is particularly useful during testing. If a trigger is configured, make sure it is enabled to prevent unexpected behavior.
Workflow Example **Store Finder Workflow** * **Trigger Details**: When a user asks for the nearest store to a specific location. * **Example User Questions**: * "Where is the closest store?" * "Can you find a store near me?" * "Find the nearest Lumine Jewels store." * "Show me the closest store to Milan."

Trigger configuration

## Top Section & Settings The settings in the top right corner of the workflow area are identical to those found in the agent area.\ This section provides key information and settings to define and optimize your virtual assistant's behavior, helping you configure and fine-tune its performance.

Top Section of the Worfklow Area

#### Workflow Name The workflow name should be **clear and descriptive**, making its purpose immediately obvious. Example: * ✅ “Store Locator Workflow” (clearly indicates that the workflow helps users find nearby stores) * ❌ "Search Workflow" (too vague) #### Last Modified Information This section automatically displays details about who last modified the workflow and when the modification occurred for version tracking. #### Settings (Top Right Button) The Settings menu includes essential toggles that define how users interact with the assistant.

Settings

#### User Feedback Toggle The User Feedback Toggle **allows users to rate the agent’s responses with a thumbs-up or thumbs-down option**. When enabled, a feedback request appears at the end of each response. Based on user reactions, the agent can connect to different workflows: a positive rating can trigger another agent or workflow, such as offering follow-up suggestions, while a negative rating can prompt a response, ask clarifying questions, or redirect the user to a human agent. {% hint style="info" %} As a best practice, it is recommended to disable feedback requests for intermediate workflows and secondary agents, ensuring that **feedback is collected only on final responses** rather than on clarification steps or data collection prompts. {% endhint %} {% hint style="info" %} 📊 Want to learn more about collecting and analyzing feedback? Check out our Analytics guide: [Analytics](/getting-started/workspace/analytics.md). {% endhint %} #### Typebar Settings The Typebar toggle lets you control how users interact with the agent: * **Enabled** (default): users can type free text at any point in the conversation. The typebar appears at the bottom of the chat, with a customizable placeholder message. * **Disabled**: the typebar is hidden. Users can only interact through the structured options you provide (e.g. [Quick Reply](/getting-started/agents-workflows-and-triggers/blocks/action-blocks/quick-reply-block.md) buttons, [Cards](/getting-started/agents-workflows-and-triggers/blocks/message-blocks/card-block.md), or other clickable elements). Disabling the typebar is useful when you want to **guide users through a structured flow** — for example, confirmation steps, multi-choice menus, or handover forms — where free text input could break the intended path. {% hint style="info" %} The Typebar setting defined at workflow level overrides the default set in the [web chat widget configuration](/build-your-ai-agents/configure-and-install-the-web-chat.md) for the duration of that workflow. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guide.indigo.ai/getting-started/agents-workflows-and-triggers/workflows.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.