# Register a Workflow for Bot Conversational Triggers You can associate Workflows with your application/bot so that the Workflow is triggered when words in the application/bot conversation match words indexed to match the workflow. **Note:** Non-conversational workflows (that are initiated by Event Triggers) do not need to be registered with the application/bot. Workflows and Hyperfllows that you do not want to be triggered conversationally should NOT be registered. ### **To Register a Workflow:** 1. Navigate to **Settings > AiseraGPT**. 2. Choose one of your existing applications/bots. If there are published Workflows for your tenant, there will be a **+ Add Workflow** button below the **Data Sources** section. 3. Click **+ Add Workflow** and choose one of the workflows in the **AI Workflow Studio** list. This action runs the flow indexer that creates the tags so the Workflow can be triggered by the application/bot conversations. #### **Ability to Search Workflow/Hyperflow Registries** When a workflow or hyperflow is associated with an application/bot, it is added to the Registry for that application/bot. A search field at the top of the Workflows / Hyperflow registry section of the spplication/bot Details page allows you to search for associated workflows and hyperflows by name. ### **To Unregister a Workflow:** 1. Navigate to **Settings > AiseraGPT**. 2. Choose one of your existing applications/bots. 3. Click the **X** at the end of the row for the workflow that you want to dis-associate from your application/bot.
### **To De-Activate a Workflow:** 1. Navigate to **Settings > AiseraGPT**. 2. Choose one of your existing applications/bots. 3. Un-toggle the **Activate** switch. This will keep the workflow available for your application/bot, but it will not activate if the application/bot conversation includes one of the indexed words or phrases.
The **Registered Flows** section of the **AiseraGPT Details** window contains a tab for **Workflows** and a tab for **Hyperflows**, a **Scope** column that tells you whether the workflow or hyperflow is available to the entire **Tenant** or only to the **Application**, a column that tells you whether the workflow or hyperflow is Active, and a button at the bottom that you can use to **Add a Workflow**.The extent of your abilities to display workflow and hyperflow information for your application/bot depends on your permission level within your Aisera Gen AI Platform. **Actions per permission level are:** * **User Role - AiseraSSO Admin (AiseraGPT - Read/Write)** * Able to view Flow Registry (Workflows and Hyperflows) * Able to update Flow Registry (Add, remove, activate and inactivate workflows and hyperflows) * **User Role - Customer Account / Admin (AiseraGPT - Read/Write)** * Able to view Flow Registry (Workflows and Hyperflows) * Able to update Flow Registry (Add, remove, activate and inactivate workflows and hyperflows) * **User Role - Customer Account / Helpdesk User (AiseraGPT - Read Only)** * Able to view Flow Registry (Workflows and Hyperflows) * UNABLE to update Flow Registry (Add, remove, activate and inactivate workflows and hyperflows) * **User Role - Customer Account / IT User (AiseraGPT - No Access)** * UNABLE to view any AiseraGPT details or Flow Registry * UNABLE to update Flow Registry (Add, remove, activate and inactivate workflows and hyperflows) ### **Manual Flow Search Reindex for Conversation 2.0 Bots** For Conversation 2.0 bots, you can manually trigger a Flow Search re-index directly from the UI when you have to make any changes to the workflows that your application/bot is using. Running the index manually is useful if you have made changes to Workflow or Hyperflow descriptions or when Workflows or Hyperflows have been added or removed from the Flow Registry, since these changes do not take effect until a reindex is completed. To trigger the reindex, navigate to **AI Automation > AI Workflow Studio**, click **Actions** on top right and then click **Run Flow Indexing**. Allow approximately 10 minutes for changes to take effect before testing the Workflow or Hyperflow. ### **Workflows Validate Registration Before Deletion** Both Tenant and Application workflows are validated before a workflow can be deleted. #### **Tenant-Level Scope** If you attempt to delete a registered, tenant-level Workflow you will receive the following message in the Aisera Admin UI: `This Workflow cannot be deleted because it is currently registered in one or more applications. Please remove it from Registered Flows before attempting deletion.` #### **Application-Level Scope** If you attempt to delete a registered, application-level Workflow you will receive the following message on the UI: `This Workflow cannot be deleted because it is currently registered in the application. Please remove it from the Registered Flows before attempting deletion.` --- # 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://docs.aisera.com/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio/register-a-workflow-for-bot-conversational-triggers.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.