Included in every Matimo Workbench plan

Compose agent
workflows, visually.

Matimo Studio is the visual AI workflow automation builder inside Matimo Workbench - a drag-and-drop canvas with 13 node types for ops teams, backed by a REST API that hits the exact same execution engine for the engineers extending it.

13 node types
Canvas + REST API - same engine
Matimo governance built-in
Webhooks + scheduled execution
Matimo Studio — Procurement Approval Workflow v3 LIVE EXECUTION
Node Library (13)
Trigger
Agent
Tool
Condition
Output
Governance
🛡 Matimo Policy
Trigger — Scheduled (daily 09:00)
Node type: Trigger · Tenant: acme-corp
DONE
Agent — Spend Classifier
Node type: Agent · Reasoning: Plan-and-Execute
RUNNING
Condition — Spend > $5,000?
Node type: Condition · Routes to Switch node
QUEUED
Output — Notify + Log Decision
Node type: Output · Slack + Audit Log
QUEUED
Execution Trace
StatusRunning
Nodes used4 / 13 types
TriggerScheduled
Latency1.24s
Tenantacme-corp
AuditLogged ✓
API parity
Same engine, either way POST /v1/workflows/run
Canvas and API share one execution path

Ops teams build it.
Engineers extend it.

Most workflow tools force a choice: a visual builder for non-engineers, or an SDK for developers - with two codebases to keep in sync. Matimo Studio's canvas and its REST API drive the same execution engine, so nothing drifts between them.

No-code for operations teams

Drag nodes onto the canvas, wire them together, and deploy - no engineering ticket required to change how a workflow behaves.

Full REST API for engineers

Every workflow built on the canvas is callable via API, and every API-defined workflow renders on the canvas. One source of truth.

Governed at the node level

Tool and Agent nodes inherit Matimo's policy checks automatically - risk classification, HITL gates, and audit logging apply however the workflow was built.

13 node types.
Every workflow you actually need.

Matimo Studio isn't a toy canvas with a handful of shapes. Every node type maps to a real execution primitive - the same ones available through the API.

Agent Node — Your Reasoning Engine of Choice

Drop in an agent backed by any of Matimo Workbench's 16 reasoning engines and 5 LLM providers. Configure personality, memory, and knowledge grounding per node - no separate deployment.

16 reasoning engines 5 LLM providers

Tool & MCP Nodes

Call any of Matimo OSS's 139+ tool actions, or connect any MCP server - HTTP, WebSocket, or stdio. Any Claude Desktop extension works immediately.

139+ tool actions

HTTP Request Node

Call any external API directly - no wrapper tool required. Headers, auth, and payload templating built into the node.

Any REST endpoint

Condition & Switch Nodes

Branch workflow logic on agent output, node data, or external signals. Switch nodes route across more than two paths for multi-outcome decisions.

Conditional routing

Loop Node

Iterate over collections - batches of records, list items, retry attempts - without unrolling logic into repeated nodes.

Iteration Retry logic

Function Node

Drop into custom code for the transformations a visual node can't express - full escape hatch, still governed and logged like every other step.

Custom code

Data Node

Map, transform, and validate the data passing between nodes - schema-aware, so downstream nodes get exactly the shape they expect.

Transform & validate

Merge & Integration Nodes

Combine parallel branches back into one path, or connect straight into enterprise systems - HubSpot, Slack, Notion, and more - as first-class workflow steps.

Parallel branches

Trigger & Output Nodes

Start workflows from a webhook, a REST call, or a schedule (cron - daily, weekly, custom cadences). Finish with structured output to Slack, email, or any downstream schema - every run logged with tenant context.

Webhook triggers Scheduled execution Structured output

Every node,
governed by default.

Matimo Studio is architected on top of Matimo OSS. Tool and Agent nodes inherit policy checks, RBAC, and audit logging automatically - workflow authors don't wire governance in separately, and can't accidentally leave it out.

For enterprises that need centralised policy management across every workflow, Matimo Governance extends this further with Shadow Mode, Emergency Stop, and one-click SOC2/HIPAA/GDPR audit exports.

Explore Matimo Governance →
Matimo Studio
Matimo Studio — Canvas + API
13 node types · Drag-and-drop · REST API parity
▼ governed by
Matimo — Governance Layer
Policy registry · Tool RBAC · HITL approval · Audit trail
▼ runs inside
⚙️
Matimo Workbench Runtime
Multi-tenant execution engine · Cost tracking · Audit trail

Built for the people who
actually own the workflow

AI / Automation Teams

Compose workflows without waiting on engineering

Drag nodes onto the canvas, connect enterprise systems, and deploy to production - no infrastructure to manage, no governance requirements to fight.

Engineering Teams

Extend via API without reinventing the stack

Every node type is addressable through the same REST API operations teams use on the canvas. Build programmatically, or hand off to ops - same execution engine either way.

IT / Security / Compliance

Every workflow, governed the same way

Tool and Agent nodes route through Matimo's policy engine regardless of who built the workflow or how. Nothing bypasses governance because it was built visually.

What's actually
in the canvas

13
Node types - Agent, Tool, HTTP Request, Condition, Switch, Loop, Integration, Merge, Function, Data, Output, Trigger, MCP
1 engine
Shared execution engine - canvas-built and API-built workflows run identically
139+ tools
Tool actions available to every Tool node, via Matimo OSS's 10 provider packages
100%
Node-level governance coverage - policy checks apply to every Tool and Agent node by default
Included in Matimo Workbench

Ready to build your
first workflow?

Matimo Studio ships with every Matimo Workbench plan - Freemium included. Sign up and start building on the canvas, or explore the full Workbench platform first.

Need governed deployment at organisation scale? See Matimo Governance.