Connect Codex to n8n
Codex reaches n8n through one Flowplane address. You add n8n once in Flowplane, add that address to Codex, and sign in. Find and run the n8n workflows you made available to assistants, on n8n Cloud or your own server, with your approval by default.
- Tools
- The app’s own set
- Sign-in
- Own account or shared key
- Approval, by default
- Changes wait for you
- MCP server
- The app’s, passed through
- 1
Add n8n in Flowplane
In the Flowplane console, add n8n, type the address you open n8n at, and sign in with n8n. For an n8n inside your network, choose a tunnel and use an access token.
Sign in with your n8n account (OAuth), the preferred way, so the assistant acts as you. If your n8n offers no sign-in for assistants, you can choose to paste an access token from n8n (Settings, Instance-level MCP) instead. A workflow runs with the rights of the n8n user who signed in or made the token. Flowplane keeps the login sealed; the assistant never sees it.
- 2
Add Flowplane to Codex
Your address is shown in the Flowplane console; it looks like
https://mcp.flowplane.eu/<your-label>- Add the server with the first command below.
- Sign in with the second: your browser opens Flowplane; sign in and allow Codex.
- In the IDE extension: MCP servers › Add server, choose Streamable HTTP, paste
https://mcp.flowplane.eu/<your-label>, then Authenticate.
codex mcp add flowplane --url https://mcp.flowplane.eu/<your-label> codex mcp login flowplane - 3
Ask Codex
- “Which n8n workflows can you run for me?”
- “What does the “New lead to CRM” workflow do, and what does it need as input?”
- “Run the weekly sales report workflow.”
- “Start the onboarding workflow for our new colleague Sara Peeters.”
What Codex can do in n8n
n8n runs the automations of many teams, on n8n Cloud or on their own server. Through Flowplane an AI assistant can search the workflows you made available in MCP and look at them, and run one, which waits for your approval by default. On n8n 2.13 and later it can also build or edit workflows, which also waits for your approval by default.
Yes: n8n has its own MCP server built into every instance (instance-level MCP), which an owner or administrator turns on. Flowplane connects to your n8n’s own server and passes its tools through, so reads are allowed and anything that runs or changes a workflow waits for your approval by default.
Questions
- What do I need to turn on in n8n?
- An owner or administrator opens Settings, Instance-level MCP and turns it on. Then, for each workflow to share, turn on “Available in MCP”. The assistant sees only those workflows.
- Can the assistant run any workflow without asking?
- Not by default. Searching and reading workflows are allowed; running, building or editing a workflow waits for your approval by default. n8n’s tools are treated as changes unless they say they only read. Use an n8n account that can see only what should be shared.
- Does Codex see the password or key for n8n?
- No. You sign in to n8n through Flowplane, which keeps that sign-in sealed. Codex only gets a Flowplane sign-in for you, which you can revoke in the console.
- Can Codex change things in n8n without asking?
- Not by default: reads are allowed and anything that changes something in n8n waits for your approval. Your workspace’s rules can make that stricter or looser.
- Connect Claude to n8n→
- Connect Claude Code to n8n→
- Connect ChatGPT to n8n→
- Connect Cursor to n8n→
- Connect GitHub Copilot to n8n→
- Connect Mistral Le Chat to n8n→
Flowplane is not affiliated with or endorsed by n8n’s maker; the name and logo only identify the app. Pricing
Let your AI work with your data. Safely, from today.
Free for yourself, set up in a minute. For your team or company, we’re happy to help you get started.