Workflows
Turn fixed steps into a workflow
Describe the flow in chat or drag nodes onto the canvas. Models, knowledge, tools and agents each become a step. Test-run it, then publish.
Made for work with fixed steps
Every step on the canvas
Each node shows which model it uses, which source it reads and which tool it calls. Changing the flow means changing the canvas.
An agent can be a step
Hand judgment and drafting to an agent, and keep exact checks in conditions and code, all in the same flow.
Build once, call it anywhere
Once published, run it by hand, put it on a schedule or let agents and Evose AI call it during a task.
From a description to a flow that runs
Three steps to a workflow you can run again and again.
- 01
Describe the flow
Say what comes in, which cases to split and what comes back. The Builder lays out and connects the nodes, and you can drag them to change it.
- 02
Test-run it
Run it on a real input. Open any node to see its input, output and duration. Failed nodes are marked.
- 03
Publish
Publish a version. Later edits stay in the draft, and schedules, agents and Evose AI always call a published version.
Nodes on the canvas
Drag any node onto the canvas to use it.
AI
LLM writes from your prompt. Knowledge Retrieval finds the passages in your knowledge bases that best match a question.
Logic
Condition Branch routes by variable values and Intent Classification by what a message means. Batch Processing handles each item in a list, and Loop builds each round on the last.
Data
Code Execution runs JavaScript or Python. The group also has Template Conversion, Variable Aggregation, Document Extraction and Parameter Extraction.
Network and tools
HTTP Request calls any API. MCP, plugin and marketplace tool nodes call tools already connected in your workspace.
Agents and workflows
An Agent node hands a step to one of your agents, which calls its own tools to finish it. A Workflow node runs another workflow as one step.
Flows inside a chat
Orchestrated Agents use the same canvas, plus Direct Reply and Form Input nodes to ask the user step by step in a conversation.
Ways to use it
Email triage
Send each customer email down the right path by issue type.
Prompt “Build a workflow for customer emails. Pull out the order ID and issue type, check the subscription for refunds and have Leo draft a reply, and answer everything else from the help center. Save replies as drafts and don't send them to customers.”
Batch extraction
Do the same thing to every file in a batch and collect the results in a table.
Prompt “Build a workflow that reads the 20 contracts I upload and pulls the client, amount and end date from each into one table. Leave fields it can't read empty and flag them. Don't guess.”
Weekly numbers
Pull the data, run the math and write it up.
Prompt “Build a workflow that calls our orders API for last week's data, uses code to work out revenue and week-over-week change per plan, then writes a short summary. Flag numbers that don't add up and never change the source data.”
A record of every run
Test runs and live runs stay in the run history, so you can find the step that went wrong.
- Replay node by nodeOpen any node to see its input, output, duration and status. Branches that didn't run are marked too.
- Errors have a fallbackSet error handling on a node so a failure takes an error branch or carries on, instead of stopping the flow halfway.
- Drafts don't touch the live versionSchedules and agents call the published version. Edited drafts take effect only when you publish again.
Questions
Turn your next repeated task into a workflow
Start with a description and publish once the test run passes.