Workflow Management Dashboard
The Workflow Dashboard serves as the central hub for managing all existing workflows. Users can create, edit, publish, or monitor automation processes from one interface.Create a Workflow
Click Create New Workflow to enter the Workflow Playground a visual design environment where automation logic is built using pre-defined components.1. Open the Playground
- Click Create New Workflow or select an existing workflow to modify.
- The visual canvas opens, displaying a Components Panel on the left and a Design Canvas in the center.
2. Drag Components
- From the left-hand Components Panel, drag and drop desired components (e.g., Chat Input, If-Else, DocuChat, Run Agent, etc.) onto the canvas.
3. Connect Components
- Use arrows to connect output fields of one component to input fields of another.
- The flow defines the execution order and data mapping between steps.
4. Configure Each Component
- Click on a component to open its configuration panel.
- Fill required fields such as API Key, Model Selection, Query, or Condition Parameters.
5. Test & Publish
- Use the Preview/Run feature to test your workflow.
- Click Publish when ready to make it active.
Workflow Components
Each component in the Components Panel plays a specific role. They are grouped into functional categories for easy navigation.Component Categories Overview
Component Details
Agent
Agent
Chat
Chat
Scope
Scope
Control
Control
Helper
Helper
LLM
LLM
Logic
Logic
Processing
Processing
Gmail
Gmail
Jira
Jira
SalesForce
SalesForce
ServiceNow
ServiceNow
Variable
Variable
Workflow Execution Flow
A workflow executes step by step, following the defined connections:- Input: Captured via Chat Input or API trigger.
- Processing: Handled by LLMs, Agents, or external integrations.
- Logic Handling: Decisions made by If-Else or Loop components.
- Output: Final message displayed via Chat Output or logged in connected systems.
Best Practices
- Keep workflows modular reuse existing templates for common automations.
- Validate each node before publishing.
- Use naming conventions (e.g., “WF_SupportTicket”) for clarity.
- Regularly review published workflows for optimization.

