Can AI agents automate FME Flow?

FME Flow is automatable today through REST API V4 on a Flow instance the organization already runs, whether self-hosted or FME Flow Hosted on AWS. The public V4 spec is Safe's stable JSON REST surface and documents jobs, tokens, repositories, automations, schedules, streams, security, and related admin resources. Access uses API tokens created in Token Management; tokens can be scoped to a workspace or job rather than inheriting every permission of the creating user. This record is FME Flow only. FME Form desktop authoring is a separate identity. From FME 2026.2, Flow can also host one or more first-party MCP servers that expose published workspaces as MCP tools. OAuth 2.0 is available when SAML is already configured; unauthenticated MCP endpoints are also offered. Servers stay dark until they are started, and workspaces without an MCP Writer typically return only job status. MCP therefore publishes the workspaces an organization chooses, not the full V4 admin API. Automations webhook triggers accept POST, PUT, or DELETE bodies. An official SDK, a first-party CLI, workflow connector catalogs, and computer-use viability were not established.

Best path today: api · Overall automatability: 8/10