Gemini 4 Argon just launched, and n8n is one of the first companies to integrate the model. You can use it with your existing n8n workflows and build new ones with it. There are three ways to do this.

Model Context Protocol (MCP): Build workflows from your favourite AI tool

MCP is an open standard governed by the Agentic AI Foundation (AAIF) that lets your AI tools connect to external applications and data sources. n8n has a built-in MCP server that works with any MCP client, so you can build your own workflows from your favourite AI tool. You need access to Gemini 4 Argon in your developer tool and an idea of what you want to build.

Setup takes a couple of minutes. Turn on instance-level MCP in your n8n instance, then add your server URL to any MCP-compatible tool, whether that's a chat app, a coding agent, or an IDE. Many tools support one-click setup and sign in with OAuth or use an API key.

Example use case: You're in your IDE building a new signup form, and the webhook is ready. You ask your agent: “Build me an n8n workflow that catches new signups from this webhook, drops them into our CRM, and fires off a welcome message in Slack.” A minute later, the workflow is in your n8n workspace, built and tested. It stops short of publishing and asks first, so you stay in the loop.

Bring Your Own Key (BYOK) with the n8n Assistant

The n8n Assistant is a chat-based agent that builds, edits, tests, and debugs workflows from plain language. BYOK means it runs on an AI provider account you already hold, rather than a model picked for you. How you set it up depends on where your n8n instance lives.

On self-hosted: Supply your own key and decide where your data and model calls go. Drop your key into the instance's settings once, and the Assistant runs on that model. One account, one model, one context. The Assistant doesn't have a native Gemini option yet, so reach Gemini through OpenRouter or through Google's OpenAI-compatible endpoint (base URL: https://generativelanguage.googleapis.com/v1beta/openai/).

On n8n Cloud: There's nothing to set up. The Assistant runs on n8n Assistant credits, and the workflows it builds can use Gemini 4 Argon through Gateway credits.

n8n Agent: Let AI handle the heavy lifting

An agent is a model handed a goal and a toolkit. It works out the steps to reach the goal on its own.

In n8n, set up an agent and use a model such as Gemini 4 Argon for the reasoning. Plug in the tools it may use (any node, API, or sub-workflow), and optionally add memory so it keeps context. The agent then decides which tool to call next, loops, and stops when the task is done. Gemini 4 Argon is available as a model for your Agents and in the standalone Google Gemini node from launch. On n8n Cloud, you can also use it through Gateway credits, so you don't need a separate provider account or extra billing. More on how AI agents work in n8n: https://n8n.io/ai-agents/

Why use one: Rigid, step-by-step workflows break when input gets messy. An agent absorbs the judgment calls, the rest of the workflow stays predictable, and you still control which tools the agent can reach.

Example use case: You get a support email. The agent reads it, pulls the customer record from your CRM, and cross-references your help docs. It then drafts a reply, sets the ticket priority, or posts a Slack flag for a human to handle.

Takeaways

• Connect Gemini 4 Argon to your IDE or chat tool through n8n's MCP server to generate workflows without leaving your tool.
• Self-hosted users can add their own key to the n8n Assistant, using OpenRouter or Google's OpenAI-compatible endpoint for Gemini.
• On n8n Cloud, Gateway credits let you use Gemini 4 Argon in both the Assistant-built workflows and Agents with no separate provider account.
• Use an n8n Agent when workflows need judgment calls, and keep the tool list limited to control what the agent can reach.