Multi-instance routing is the reason to pick this one: each environment carries its own host and API key, the instance argument picks between them per call, and defaultEnv decides where an unqualified call lands — which makes promoting a workflow a conversation rather than an export and an import. Worth knowing before you plan around it: n8n's API does not support partial workflow updates or reading credentials back, so updates replace the whole workflow and a credential change is a delete followed by a create; the tools say so rather than pretending otherwise.
A management layer over the n8n public API. Every tool takes an optional instance argument, so one server addresses several n8n environments configured side by side rather than one per connection.
- Workflows created from nodes and connections, read, updated, deleted, activated and deactivated by id
- list_workflows returns metadata only — id, name, status, dates, node count, tags — with an active filter, so listing a large instance does not drag the whole payload back
- execute_workflow runs one by id with optional runData, for testing without waiting on its trigger
- Executions listed with status, workflow and project filters and a cursor, read individually with or without their data, and deleted
- retry_execution starts a new run from a failed one, and refuses executions that did not end in error
- Tags created, listed, read, renamed and deleted, which is what keeps workflow lists navigable at scale
- list_credentials returns credential metadata — id, name, type, node access, timestamps — and never the secrets themselves
- create_credential and delete_credential manage credentials for external services; get_credential_schema returns the field definitions, types and validation rules for a type such as httpBasicAuth or googleDriveOAuth2Api
- Tools whose n8n endpoints do not exist answer with guidance instead of failing silently: patch_workflow points at update_workflow, and credential reads and updates explain the delete-and-recreate path
An n8n instance with the public API enabled and an API key for it — tested against n8n v1.82.3 and later. Node.js v14 or higher (v18+ recommended) and npm v7+; it runs as npx @kernel.salacoste/n8n-workflow-builder. One instance is configured with N8N_HOST and N8N_API_KEY in a .env file; several go in a .config.json listing each environment with its own n8n_host and n8n_api_key, plus defaultEnv to decide which one a call without an instance argument reaches. MIT.
One command plus a key — npm install -g @kernel.salacoste/n8n-workflow-builder, then supply credentials