Canvas & Workflows
The canvas is Conduet's visual workflow editor. It provides a drag-and-drop interface for designing conversation flows by placing steps, connecting them with edges, and configuring each step's behavior.
Workflows
A workflow is a connected series of steps that define how your agent behaves. You can have as many workflows in a project as you like — a primary one that runs when a conversation starts, plus any number of supporting flows you can hand off to.
Steps
Steps are the building blocks of a workflow. Each one appears as a card on the canvas with input and output handles you can drag between. Click any step to open its settings panel and configure exactly how it should behave. Every workflow starts at the Start step and ends at one or more End steps — everything in between is up to you.
Connections
Connections link steps together and define what happens next. Most steps just flow into the next one, but branching steps like Condition and Buttons have multiple outputs — one for each possible path — so your conversation can adapt to what the user says or to the data you've collected along the way.
Working with the Canvas
Adding Steps
Drag a step type from the palette onto the canvas, or right-click the canvas to add a step at that position. Each step is automatically assigned a unique ID and default configuration.
Creating Connections
Click and drag from an output port to an input port to create a connection. The canvas validates that connections form a valid graph (no orphaned steps in the main execution path).
Configuring Steps
Click a step to open its properties panel on the right side. Each step type has different configuration options: agent steps have system prompts and tool selections, message steps have content fields, condition steps have branching rules, and so on.
Organizing the Canvas
Drag steps to reposition them. Use zoom and pan to navigate large workflows. Steps store their canvas position so your layout is preserved between sessions.
Common Workflow Patterns
Linear Flow
Start → Message → Listen → Agent → End. The simplest pattern: greet the user, wait for input, process with an agent, and end. Good for single-turn Q&A.
Branching with Conditions
Start → Listen → Condition (check variable) → Branch A / Branch B. Route the conversation based on user input, variable values, or any other condition. Each branch can have its own sequence of steps.
Menu with Buttons
Start → Message → Buttons (Sales / Support / FAQ) → separate workflows per choice. Present users with options and route to specialized sub-flows based on their selection.
Agent with Tools
Start → Agent (with KB search, API tools, web search enabled). The agent autonomously decides when to search the knowledge base, call APIs, or use other tools to fulfill the user's request. Best for the agentic framework.
Multiple Workflows
For complex agents, you can split logic across multiple workflows and hand off between them as the conversation progresses. Pass data along when you do, so each workflow picks up exactly where the previous one left off. It's the easiest way to keep big agents modular and reusable.