Resources · n8n integration

n8n Google PaLM Language Model nodeConfigure Google PaLM Language Model in n8n.

The n8n Google PaLM Language Model node turns a prompt into generated text without leaving your workflow. Version 1 exposes 5 parameters: the model itself, a token ceiling, and three sampling controls. Nothing to authenticate on the node, which suits builders already running n8n.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Google PaLM Language Model node actually do?

It runs a Google PaLM completion on the items that reach it. You pick the model which will generate the completion, you decide how long the answer can get, and you steer how predictable the wording should be. The node ships inside the n8n AI package, so it is there on n8n Cloud and on a self-hosted instance alike, with nothing to install and no extra cost on the n8n side.

Drafting comes first. A workflow reads fresh rows, sends each one through the node with Sampling Temperature kept low, and writes a factual one-line summary back beside the original row in Google Sheets. Same input, same tone, every run.

Classification is the second shape. Maximum Number of Tokens stays small because the answer is a single label, and Top K cuts the improbable words that turn a clean label into a sentence. The routing happens after the node, on the field it returns.

Variation is the third. Top P widens the pool of candidate words, so a batch of short product blurbs does not read like 5 copies of one sentence. Expressions such as {{ $json.prompt }} feed each item its own text, and a required field left empty stops the node instead of generating noise.

When to reach for something else. This node produces one completion per incoming item and nothing more. If you need a loop that picks its own next step and calls tools on its own, the root node is AI Agent, and a model sub-node plugs onto its port. If the answer has to come back as strict JSON, an Auto-fixing Output Parser belongs in that chain. Another provider means another node, such as OpenAI.

Limits worth knowing before you build on it. The node carries no credential of its own and has no sub-node port, and the catalog lists a single version, so an older workflow shows the same 5 parameters. Google bills its own API calls under its own terms; n8n adds nothing on top. Still weighing platforms? The n8n review covers that ground.

Parameters

Which parameters matter on this node?

The Google PaLM Language Model node has 5 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

01

Model

modelName

What you see in n8n

Notes & use cases

This is where the node learns what to call. The value names the model which will generate the completion, and it applies to every item the node processes in that execution.

Key parameters

  • Model: the model which will generate the completion. Leave the stored value alone until a workflow gives you a reason to change it, or pass {{ $json.model }} when the choice travels with the incoming item.
Use cases
a support queue where short acknowledgements and long case summaries go through two copies of the node, each pinned to its own model.
02

Maximum Number of Tokens

options.maxOutputTokens

What you see in n8n

Notes & use cases

Length gets its ceiling here. The field sets the maximum number of tokens to generate in the completion, tokens being the chunks a model reads and writes rather than whole words.

Key parameters

  • Maximum Number of Tokens: the cap on generated text. Keep it tight for a one-line label, raise it for a paragraph, or read it from the item with {{ $json.maxTokens }}.
Use cases
a notification sent to Slack, where a capped completion keeps the message readable in the channel.
03

Sampling Temperature

options.temperature

What you see in n8n

Notes & use cases

Predictability lives on this dial. It controls randomness: lowering it results in less random completions, and as the temperature approaches zero the model becomes deterministic and repetitive.

Key parameters

  • Sampling Temperature: near zero for extraction and reformatting, where two runs on the same row should agree; higher when repetition is the thing you are trying to avoid.
Use cases
rewriting raw order notes into clean shipping instructions, where a deterministic output makes the downstream mapping safe.
04

Top K

options.topK

What you see in n8n

Notes & use cases

Think of it as a filter on the candidate words. It is used to remove long tail low probability responses, the odd choices that make an otherwise usable answer wander.

Key parameters

  • Top K: it defaults to -1, which disables it, so nothing is filtered until you set a value. Worth reaching for when completions drift off format rather than off topic.
Use cases
tagging inbound messages, where the answer must stay inside a known vocabulary instead of inventing a new label.
05

Top P

options.topP

What you see in n8n

Notes & use cases

Diversity gets its own control, through nucleus sampling. A value of 0.5 means half of all likelihood-weighted options are considered, so the pool the model draws from shrinks or widens with the number.

Key parameters

  • Top P: the recommendation is to alter this or Sampling Temperature, but not both, since the two overlap and moving them together makes results hard to read.
Use cases
generating several subject line options for the same campaign before a human picks one.
Need help

Need help automating Google PaLM Language Model with n8n?

A person reads every message.

FAQ

Google PaLM Language Model and n8n: common questions

01Is the n8n Google PaLM Language Model node included for free?
Yes. It belongs to the n8n AI package, @n8n/n8n-nodes-langchain, which ships with n8n. There is nothing to install and no extra charge on the n8n side, whether you work on n8n Cloud, the hosted offer run by n8n, or on your own self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, so a flow built on a laptop moves to Cloud without rework. What does cost money sits on the other side: Google bills its own API calls according to its own terms, and n8n adds nothing on top of that.
02What do you need for it to work?
Nothing on this node itself. It has no credential and no Authentication selector, which is why the page has no connection section: there is simply no account to link here. The credential for the provider is carried by the model sub-node that gets plugged in, following the way n8n organizes its AI nodes, where a root node receives the workflow items and sub-nodes attach to its ports, one type per port. On this node your setup work is the 5 parameters and the prompt data you feed it, usually through an expression such as {{ $json.prompt }} pointing at a field of the incoming item.
03What are the limits of this node?
It generates text on the items that reach it, and that is the whole job. It executes like a regular action node, one pass per incoming item, and it has no sub-node port of its own, so you do not hang a memory or a tool off it. The catalog lists version 1 as the highest version, so there is no newer variant with extra options waiting behind an upgrade, and an older workflow shows the same 5 parameters. Each parameter is optional, but a field marked required anywhere in the chain blocks execution when it is left empty.
04What should you plug in to get started?
Start with the node alone on a small batch. Give it a prompt through an expression, set Sampling Temperature low so two runs on the same input agree, and check what comes back before wiring anything downstream. Once the output is stable, decide whether the workflow needs more than one completion per item. If it does, the root node to look at is the AI Agent, which drives the loop and calls tools, with a model attached to its port. If the answer must be valid JSON for the next node, that is where an output parser earns its place.
05n8n or Make for this kind of AI step?
It depends on what you weigh most. Make, formerly Integromat, is a hosted automation platform with no self-hosting option and pricing charged per operation, which makes cost predictable when volume is low and less so when a workflow fires constantly. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, and the same workflow runs in either place, which matters when the text you send to a model should not leave infrastructure you control. Visual logic differs too, so the honest answer is to try the shape of your own flow on both.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.