Automate Basics
Automation · n8n

n8n adds Gemini 4 Argon to agents and workflow-building options

By Automate Basics, written with AI from n8n's original

· 2 min read

Hand holds a workflow tablet above printed support emails and checklist
Image: AI-generated illustration.

n8n says users can choose Gemini 4 Argon for agents and its Google Gemini node. They can also build workflows with the model through an MCP-connected tool or, on self-hosted instances, connect it to the n8n Assistant through another provider route.

What changed in n8n

n8n says Gemini 4 Argon is available as a model for its agents and in its standalone Google Gemini node. An agent can use the model to decide which permitted tool to call next during a workflow. n8n also describes ways to use the model while building workflows, rather than only inside workflows that run later.

Users with access to Gemini 4 Argon in an MCP-compatible tool can connect that tool to n8n’s built-in MCP server and ask it to create a workflow. Separately, the n8n Assistant can build, edit, test and debug workflows from plain-language requests. The Assistant does not yet offer a native Gemini option, so using Gemini with it on a self-hosted instance requires a route through OpenRouter or Google’s compatible endpoint.

Who can use Gemini 4 Argon in n8n?

n8n describes options for both self-hosted users and n8n Cloud users, but they work differently. Self-hosted users can supply their own provider key for the Assistant and choose where its model calls go. To use Gemini 4 Argon that way, they need one of the indirect connections n8n describes. People building workflows through MCP need access to the model in a compatible tool and must connect that tool to their n8n instance.

On n8n Cloud, the Assistant uses Assistant credits, while workflows can use Gemini 4 Argon through Gateway credits without a separate provider account. n8n does not give plan eligibility, credit allowances or prices in this announcement, so the cost of a particular setup is not clear from the source.

How do I try Gemini 4 Argon at work?

A support email is a useful first task for trying a Gemini 4 Argon agent in n8n. n8n suggests an agent that checks a customer record and help documents, then drafts a reply, assigns ticket priority or flags the message for a person. Keep the agent’s permitted tools limited to what the task needs, and check the customer details, cited help material and proposed response before relying on the result.

For workflow building, try describing a small process with a clear trigger and destination, such as sending new signups to a CRM. n8n says an MCP-connected tool can build a workflow from such a request. Check the trigger, data mapping and destination before publishing. In n8n’s example, the generated workflow is left unpublished until the user approves it.

Frequently asked questions

Can Gemini 4 Argon run inside an n8n workflow?

Yes. n8n says Gemini 4 Argon is available for its agents and in the standalone Google Gemini node. On n8n Cloud, workflows can also use the model through Gateway credits without a separate provider account.

Does the n8n Assistant have a built-in Gemini option?

No. n8n says the Assistant does not yet have a native Gemini option. On a self-hosted instance, users who want to run the Assistant with Gemini can connect through OpenRouter or Google’s compatible endpoint using their own provider key.

How much does using Gemini 4 Argon in n8n cost?

The announcement does not state prices, plan eligibility or credit allowances. n8n says its Cloud Assistant uses Assistant credits and Cloud workflows can use Gemini 4 Argon through Gateway credits. Self-hosted Assistant users supply their own provider key.

Tools in this piece

Written with AI from n8n's original and published after automatic checks: every figure here appears in the original, and no sentence is copied from it. The picture is AI-generated. The original is the authority.

Source: Build n8n workflows with Gemini 4 Argon: MCP, the Assistant, and Agents, n8n, 13 Oct 2026.