Can AI agents automate n8n?

n8n is automatable today through its public REST API. The API at /api/v1 authenticates with an X-N8N-API-KEY header and can create, update, activate, and delete workflows plus manage executions, credentials, projects, tags, variables, data tables, and users. Cloud free-trial tenants cannot use the API until the instance is upgraded. Enterprise keys can be scoped; other keys have full account access. Official n8n CLI (@n8n/cli) wraps the same API from any network-reachable machine, supports --format=json, and is documented for AI-agent use. A first-party instance-level MCP server, distinct from the MCP Server Trigger node, can search, build, validate, and run workflows after an instance owner enables MCP and marks workflows Available in MCP. Clients authenticate with OAuth or a bearer API token. n8n's 2026-04-29 blog called the workflow-building MCP update a Public Preview and recommended version 2.18.4 or higher; current setup docs add OAuth client dialogs from 2.33.0 and many tool behaviors are version-gated. This record excludes UiPath, Zapier, and Microsoft Power Automate. Computer-use viability is unassessed. API, MCP, and CLI all score 7; API is the best path because it does not require instance MCP enablement, per-workflow exposure, or a publicly reachable MCP endpoint.

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