Workflows
Creating a Workflow
Section titled “Creating a Workflow”To create a workflow, you need to click on Create FloTorch Workflow button in the top right corner of the FloTorch Console. Provide a name and description for the workflow. Workflow name should be unique and can only contain alphanumeric characters and dashes (a-z, A-Z, 0-9, -).
Once a workflow is created, you will be navigated to the version configuration page, meanwhile your workflow will appear in the Workflows list.
When a workflow is created, a default version 1 is created automatically and is set in Draft state. You need to configure the workflow version and publish it to make it available for use through Gateway.
Workflow Versions
Section titled “Workflow Versions”Workflow versions are the individual configurations of a workflow. Each workflow can have multiple versions. Each version can have different agents, connections, and resources. Once a workflow version is published, it is immutable and cannot be changed.
A new version can be created by clicking on New Version button in the top right corner of the FloTorch Console or on the Workflow version configuration page by clicking on the three dots button beside the Publish button which will open a dropdown containing Create new version.
A new copy of any published or draft version (make a revision) can be created.
To create a copy of a published version, click on the Make a Revision button which is located in the top right of the page.
To create a copy of a draft version, click on the three dots button, which will open a dropdown, then select the Make a Revision option.
Configuring a Workflow Version
Section titled “Configuring a Workflow Version”Workflow versions can be configured using the instructions below:
- Identify the workflow you want to configure from the
Workflowstable. - Click on the
Actionsdropdown button and selectView Versions. - You will see a list of
Workflow versionsin a slideover table. - Click on any version number to open that workflow version configuration page, or click on a particular row to navigate to the latest workflow version configuration page for that workflow.
You will be presented with a workflow configuration canvas. You can configure the following components:
- Agents - List of agents which have been created earlier and have at least one published version.
- Knowledge Bases (RAG/Long-term Memory) - List of knowledge bases which are already created in the workspace. These can be attached to individual agents in the workflow.
- Memory - Memory systems which are already created in the workspace. These can be attached to individual agents to maintain conversation context.
- Connections/Edges - You can connect one node (agent) to another to create sequential or complex execution flows (prompt chaining).
Adding and Configuring Agents to Workflow
Section titled “Adding and Configuring Agents to Workflow”Adding Agents to the Canvas
Section titled “Adding Agents to the Canvas”- On the canvas, you can see
StartandEndnodes which are not deletable. These represent the entry and exit points of your workflow. - Click on the
Add Agentbutton, which will open a slideover showing a list of agents which have been created and have at least one published version. - Select any agent and click on the
Add Agentbutton. The agent will be added to the canvas. You can add as many agents as you want.
Configuring Agent Nodes
Section titled “Configuring Agent Nodes”- Once the agents are added, you can configure each agent node with additional resources:
- Knowledge Bases (RAG/Long-term Memory)
- Memory
- To configure an agent node, click on any agent node on the canvas. A slideover will open containing the agent’s information.
- In the slideover, you can:
- Change the agent version being used
- Select Knowledge Bases (RAG/Long-term Memory) to attach
- Select Memory systems to attach
- After making your selections, click the Save button to save the configuration.
Organizing the Canvas
Section titled “Organizing the Canvas”- You can reposition the nodes by drag and drop to create a clear visual flow.
- To delete a node, hover over the node and click on the trash icon that appears.
- To create connections (edges) between nodes, click and drag from one node to another.
- To delete edges, select the edge by clicking on it, then press the Backspace or Delete key on your keyboard.
- You can reposition, drag and drop, add and delete nodes and edges on the canvas while the workflow version is in Draft state.
- Important: Once the workflow version is published, you cannot edit or delete edges and nodes on the canvas. The configuration becomes immutable.
Once the workflow version is configured, you can publish it to make it available for use through Gateway.
Publishing a Workflow Version
Section titled “Publishing a Workflow Version”Workflow versions can be published using the Publish button which is located in the top right corner of the workflow version canvas.
Once you click the Publish button, a new form will be opened in a slideover which contains a summary field for the version and a “Mark as Latest” checkbox.
If you check the “Mark as Latest” checkbox, the current published version will be marked as the latest version for the workflow.
To publish already created versions which are in draft mode, click on the History button which is located before the Publish/Make a Revision button. A slideover will open with the workflow version list table. Click on the Publish button for unpublished versions, and click on the Mark as Latest button to mark that version as the latest version for the workflow.
Once a workflow version is published, it is immutable and cannot be changed. To make modifications, you must create a revision (copy) of the published version.
The published workflow can be used through the Gateway API in an OpenAI-compatible format as flotorch/<workflow-name>:<version>
Publishing Latest Version of a Workflow
Section titled “Publishing Latest Version of a Workflow”You can publish the latest version of a workflow by selecting a particular version:
- Identify the workflow you want to publish the latest version of.
- Click on the
Actionsdropdown and selectPublish Latestto publish the latest version of the workflow. - You will be presented with a slideover with a dropdown list of versions. Select the version you want to publish as latest and click on
Publishto publish the latest version of the workflow.
Similarly, you can publish the latest by clicking on View Versions in the Actions menu. The slideover will open with the workflow versions list, where you can publish or mark a version as latest.
Once the latest version is published, it is tagged as published and can be used through the Gateway API as flotorch/<workflow-name> without specifying the version. The system will automatically route requests to the latest published version.
Workflow API Usage
Section titled “Workflow API Usage”Using a Specific Version:
curl -X POST https://gateway.flotorch.com/v1/chat/completions \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "flotorch/customer-support:2", "messages": [ {"role": "user", "content": "I need help with my order"} ] }'Using the Latest Version:
curl -X POST https://gateway.flotorch.com/v1/chat/completions \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "flotorch/customer-support", "messages": [ {"role": "user", "content": "I need help with my order"} ] }'Best Practices
Section titled “Best Practices”- Test Thoroughly: Always test draft versions before publishing
- Version Summaries: Provide clear summaries when publishing to track changes
- Mark Latest Carefully: Only mark stable, well-tested versions as latest
- Use Descriptive Names: Name workflows clearly to indicate their purpose
- Start Simple: Begin with linear workflows before adding complexity
- Visual Organization: Arrange nodes logically to reflect the execution flow
- Resource Management: Only attach necessary knowledge bases and memory to agents
- Connection Planning: Plan the flow of data between agents before creating connections
- Version Management: Keep track of which versions are in production use
- Immutability: Remember that published versions cannot be edited - always create revisions for changes