What an agent can do in n8n
Search, run and build workflows on your own n8n instance, read their executions, and work with its data tables.
Jobs on Rush that use n8n
- What Changed in Our n8n Automations This Week? An Accounting Firm's Friday Change Log
- Review Yesterday's Failed n8n Workflow Runs Before the Store Opens
How n8n connects
n8n is a remote MCP server, published by n8n, at https://{host}/mcp-server/http. Connecting it signs in through the MCP OAuth flow on n8n's side.
From n8n: n8n's MCP documentation · source code.
Its address is your own. Before you connect, fill in {host}: Your n8n address, like yourname.app.n8n.cloud. Turn on Settings > Instance-level MCP in n8n first.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names n8n in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "n8n",
"url": "https://{host}/mcp-server/http"
}Replace {host} in url first: Your n8n address, like yourname.app.n8n.cloud. Turn on Settings > Instance-level MCP in n8n first.
Whose n8n account the agent uses
Your n8n connection is personal: it belongs to the person who signed in. A run started in the console uses that person's n8n, and a run started with an API key uses the n8n of the member who created the key.
More Developer Tools integrations
Frequently asked questions
How do I connect n8n to Rush?
Open Settings → Connections in the console and connect n8n, or send POST /me/connections with {"type":"mcp","name":"n8n","url":"https://{host}/mcp-server/http"}, its address filled in, and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my n8n account?
No. A run gets your n8n connection only when it names it in connections ("connections": ["n8n"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in n8n?
Search, run and build workflows on your own n8n instance, read their executions, and work with its data tables. 2 published jobs use it; this page lists them.
Which n8n does the agent connect to?
Yours. n8n's MCP server runs at your own address: the console asks for host before Connect, and from the API you fill it into https://{host}/mcp-server/http and send the result as url.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to