The diagram is the process — not just a picture.
A workflow defines what happens, in what order, under which conditions and when a person should step in. What you draw is what runs.
- Trigger
- Agent
- Knowledge
- Decision
- Tool
- Approval
- Result
What the diagram contains
Core automation. Human approval is a first-class node via the approval service.
Explicit nodes
Trigger, agent, retrieval, decision, tool, capability, loop, approval and response are drawn as steps. Behaviour follows the graph.
Backend catalog
Node types and contracts are defined in agent-service. The UI does not invent runtime magic.
Orchestrated run
orchestration-service executes the graph, stores run state, pauses on approval and resumes after a decision.
Authoring in admin
The live editor is the A2A canvas: select a step, inspect it, version the graph and publish a run.
Explore more
Workflow steps
The steps you can place on the canvas — from triggers and agents to approvals and actions.
Workflows
A workflow is more than a diagram. It defines what happens, in what order, under which conditions and what should happen when a human needs to step in. Create workflows from triggers, agents, knowledge retrieval, decisions, tools, loops, approvals and actions.
From prompt to action
MCP Fabric can turn a request into an actual process: Ask → Understand → Retrieve → Decide → Execute → Approve → Done. AI can retrieve the right business knowledge, make a decision, call the appropriate tools, wait for human approval when needed and continue the workflow.
Ready to move beyond the chatbot?
Build AI that understands your business, follows your processes and can actually get things done.