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.
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.
Drag nodes onto the canvas, wire them together, and deploy - no engineering ticket required to change how a workflow behaves.
Every workflow built on the canvas is callable via API, and every API-defined workflow renders on the canvas. One source of truth.
Tool and Agent nodes inherit Matimo's policy checks automatically - risk classification, HITL gates, and audit logging apply however the workflow was built.
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.
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 providersCall 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 actionsCall any external API directly - no wrapper tool required. Headers, auth, and payload templating built into the node.
Any REST endpointBranch workflow logic on agent output, node data, or external signals. Switch nodes route across more than two paths for multi-outcome decisions.
Conditional routingIterate over collections - batches of records, list items, retry attempts - without unrolling logic into repeated nodes.
Iteration Retry logicDrop into custom code for the transformations a visual node can't express - full escape hatch, still governed and logged like every other step.
Custom codeMap, transform, and validate the data passing between nodes - schema-aware, so downstream nodes get exactly the shape they expect.
Transform & validateCombine parallel branches back into one path, or connect straight into enterprise systems - HubSpot, Slack, Notion, and more - as first-class workflow steps.
Parallel branchesStart 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 outputMatimo 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 →Drag nodes onto the canvas, connect enterprise systems, and deploy to production - no infrastructure to manage, no governance requirements to fight.
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.
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.
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.