Workflow

Visual business process orchestration · 17 nodes · 4 triggers · Versioning and monitoring

Workflow is Evose's tool for process-driven automation. Compose multi-step tasks into a visual graph.

When to Use Workflow

Steps are fixed and repeatable (input varies, the process is the same)
Need batch, scheduled, or API triggers
Need multiple Agents / tools / data sources to coordinate
No need for back-and-forth user dialog

Create a Workflow

Workspace → Apps · Workflow → New
Open the canvas; default contains Start and End nodes
On the Start node, define inputs (type / required / default)
Drag in business nodes and connect them
On the End node, define outputs
Trial-run → save version → publish

8 Groups, 17 Nodes

Workflow nodes are nearly identical to Chatflow, but without the Interaction group (it doesn't dialog with a user in real time):

Group	Nodes	One-liner
AI	LLM · Knowledge retrieval	Call models, do RAG
Logic	Condition · Batch · Loop · Intent classification	Branching and loop control
Data	Code · Template · Variable · Document extraction · Parameter extraction	Process structured data
Network	HTTP	Call external APIs
App	Agent · Workflow	Nested calls into other apps
Tool	MCP · Plugin · Marketplace	Connect external capabilities
End	End	Terminate and output

Four Trigger Modes

Trigger	When to use
Manual	Default; trigger from Workbench or API
Scheduled (Cron)	Daily / weekly / hourly — see Schedule
Event	Webhook / DB change / queue message (preview)
Conditional	Auto-trigger when a condition is met (preview)

Current MVP limitations

Some event / conditional triggers are preview only — see Schedule · MVP limits.

Collaboration Patterns

A Workflow is not an island. It often coordinates with Agents / Chatflows / other Workflows:

Pattern 1: Workflow calls Agent
  Workflow → node → Agent → reasoning → return result

Pattern 2: Chatflow triggers Workflow
  User says "generate report" in a Chatflow → Chatflow triggers a background Workflow

Pattern 3: Workflow orchestrates multiple Agents
  Workflow → Agent A (analyze) → Agent B (write) → Agent C (review) → output

Trial Run + Monitoring

Capability	Behavior
Trial run	Top right of the editor; provide test inputs and run immediately
Live status	Each node shows waiting / running / success / failure
Per-node latency	Each node shows execution milliseconds
Error logs	Failed nodes expand to show full exception + input snapshot
Run history	Workspace · Observability · Traces

Version Management

Behavior	Description
Auto-save	Drafts persist 30 seconds after each edit
Manual versions	Annotate with a version label (e.g. `v1 · initial`)
Version diff	Pick two versions to compare
Quick rollback	One-click restore to any historical version
Tags	Tag versions (`prod` / `staging`)

Publishing

Setting	Description
Visibility	Controlled via RBAC + ACL
Trigger channels	Workbench · Schedule · API · Webhook
API call	See Workflow API

A Minimal Example

Start (input.topic) → LLM (generate outline) → Batch (per chapter) → LLM (expand) → End (article)

→ Full tutorial · First Workflow

Anti-Patterns

More than 30 nodes — split into sub-Workflows; the parent only orchestrates
Stuffing big logic into a node — extract to a Code node or a Tool
Workflow → Agent → Workflow → Agent deeply nested — Traces become unreadable, costs hard to attribute; prefer linear flow

Next Steps

Hands-on → First Workflow
Scheduling → Schedule
API → Workflow API
End-to-end → Marketing automation tutorial

On this page