n8n
List, run and debug your n8n workflows and executions from agent work.
Connect it with: API key. n8n's own documentation: https://docs.n8n.io/api/authentication/.
What agents can do
Connect n8n so the agents working your tasks can reach it. With it connected, they can:
- List workflows and read a workflow's nodes and settings.
- Read executions and their errors to debug a failing automation.
- Activate or deactivate a workflow, or update it from a task.
- Manage tags, variables and credentials metadata through the n8n API.
Before you start
- An n8n Cloud plan or self-hosted instance with the public API enabled (it is on by default; the free trial of n8n Cloud has no API).
- An n8n account allowed to create API keys.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with n8n
Jaah connects to n8n with an API key, not with a sign-in button.
Connect with an API key
Find each value first:
- Base URL: Your n8n instance's address as you open it in the browser: https://your-name.app.n8n.cloud for n8n Cloud, or your self-hosted n8n's https address, with nothing after it.
- API key: n8n > Settings > n8n API > Create an API key: name it Jaah, set an expiry (and scopes on Enterprise), select Save, then copy it - n8n shows it once.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the n8n card.
- Name the secret and choose who can use it.
- Fill in Base URL, API key.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to n8n with an API key, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to n8n with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: base_url, api_key.
Tell the agent in your task description which secret to use, for example “use the n8n secret org/n8n”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at n8n once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at n8n's side too, revoke or delete the key at n8n.
Limitations
- n8n's hosted MCP server needs its own sign-in or token, which this secret does not hold: to give agents its tools, add a Custom MCP server secret with your instance's MCP Server URL (Settings > Instance-level MCP; it ends in /mcp-server/http) and its MCP token, and link it to the project.
- An API key acts as the user who created it, with that user's access to workflows.
- Self-hosted n8n must be reachable from the internet over https for Jaah's Test and agents.
- n8n's public API does not run a workflow on demand; trigger a webhook workflow instead.
- Agents can do only what the connected n8n account allows.
Troubleshooting
Test says the API key was rejected (401)
The key expired, was deleted or mistyped. Create a new key in Settings > n8n API and select Replace.
Test cannot reach n8n or answers 404
Base URL is not your instance's root, or the public API is disabled (N8N_PUBLIC_API_DISABLED). Use the address you sign in at, with nothing after it.
There is no n8n API item in Settings
Your plan has no API access (for example the Cloud trial). Upgrade, or use a self-hosted instance.
Still stuck? Select Test and read the result: it names the value n8n refused and the status it answered.
FAQ
Can agents trigger a workflow?
Through a workflow's Webhook trigger URL, which agents can call. The n8n API itself manages workflows and executions.
Does it work with self-hosted n8n?
Yes, when the instance is reachable over https from the internet.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one n8n account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.