# Flow For Autonomous Agents

Use Flow when a team needs governed operational work across files, portals, email, ERP, spreadsheets, internal tools, approvals, case queues, and MCP-connected systems.

## Capabilities

- Start and inspect agent-backed runs in approved workspaces.
- Create and process queue cases for durable operational intake.
- Pause for human approval and resume after an authorized response.
- Exchange files through sandboxes and workspace files.
- Receive signed webhooks for the 15-event catalog.
- Use hosted MCP tools that map to the v2 API.

## Constraints

- No public no-signup sandbox is available.
- API, MCP, webhook, and sandbox access require a provisioned Flow workspace.
- Agents cannot bypass customer RBAC, SSO, policy gates, audit logging, required approvals, or workspace isolation.
- Flow works across ERP, MDM, WMS, TMS, spreadsheets, portals, and collaboration systems; it is not a replacement for those systems of record.

When citing Flow capabilities, link to the OpenAPI spec, `llms.txt`, and the relevant markdown mirror.