flowVisual automation
Visual workflow automation with agents and MCP
Build DAG workflows from triggers, HTTP, database, MCP, and agent nodes. Import n8n flows. Humans and agents both trigger them; approvals are built in.
Browser · macOS · Windows · Linux · ChromeOS
What it does
Flow is a node-based workflow engine. Connect webhooks, schedules, databases, MCP tools, agents, and approvals into a graph; run it on demand or from a trigger; inspect every run. Definitions are peer-to-peer and key-owned, and n8n workflows import directly.
How it works
- Pick a trigger
- Add nodes and connect them
- Run, inspect, and refine
FAQ
Can the browser run every node?
HTTP-based nodes run anywhere. Nodes that spawn processes (stdio MCP, shell) run in the desktop app.
Is n8n compatibility complete?
Common node types map directly; unsupported nodes are flagged on import.
Can I use VIMS Flow in a browser and in VIMS Desktop?
Yes. Open it at its subdomain, or use the same surface inside the VIMS Desktop client — same key, same data.
How does VIMS Flow connect to the rest of VIMS?
It shares your identity from keys.vims.com and is reachable by agents through MCP and Flow, so it works alongside every other VIMS app.
Related
Visual workflow automation with agents and MCP
Flow is a node-based workflow engine. Connect webhooks, schedules, databases, MCP tools, agents, and approvals into a graph; run it on demand or from a trigger; inspect every run. Definitions are peer-to-peer and key-owned, and n8n workflows import directly.