Resources · n8n integration

n8n Think Tool nodeConfigure Think Tool in n8n.

Some questions deserve a pause before the answer. The n8n Think Tool node buys an agent that pause: one required parameter, and the model talks to itself before replying. It is a sub-node, so it hangs off the Tool port of a root node instead of running on its own.

Try the Think Tool node on n8nSee the 1 parameters

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Think Tool node actually do?

The Think Tool node is a tool an agent can call to reflect on a question before answering it. A tool, in an AI context, is an add-on resource the model can reach for when a request needs more than a straight reply. This one adds no external system and fetches nothing. It hands the agent room to reason out loud, which is what complex questions usually lack.

Picture an agent that reads a job queue from Google Sheets, decides what to produce for each row, then posts the result. Without a thinking step, the model commits to the first plausible plan. With the Think Tool wired to its Tool port, it lays out the constraints, checks them against each other, and only then calls the tool that writes the row back.

Second case: triage. An agent watches an inbox through Gmail and has to pick a route for every message. Some are trivially sorted. A few carry two signals that point in opposite directions, and those are the ones a thinking pass catches, before the agent fires the wrong branch and drops a reply in the wrong Slack channel.

Third case: anything the agent has to justify. When the run ends in a summary a human will read, the reasoning the node produces is what keeps the final answer from being confidently wrong. The official documentation shows the pattern on a logic puzzle: the agent walks both hypotheses, finds they converge, and answers yes with the work shown.

Now the honest part. This node does nothing on its own, and it does nothing on a simple task. If your agent looks up one value and returns it, a thinking step adds a model round trip and no accuracy. Reach for it when the agent chooses between several actions, or when the prompt contains conditions that interact. The reasoning also costs tokens on the chat model you plugged into the AI Agent, and the model provider, whether OpenAI, Anthropic, Google or another, bills those API calls under its own terms.

Two limits worth knowing before you drop it on a canvas. The node has no main input, so nothing upstream connects into it, and it never runs in isolation: it only exists once a root node accepts it on the Tool port. And at version 1 it exposes exactly one parameter, so there is no depth setting, no reasoning budget, no toggle to tune. What you shape is the description text, and that is the whole control surface.

Connections

Where does the Think Tool plug in?

n8n splits AI work between a root node, which receives the workflow items on its main input, and sub-nodes that clip onto its ports, one type of sub-node per port. Think Tool is a sub-node, so read this the other way around: it has no input of its own, only the port it attaches to.

Output (what it plugs into)

  • Toolai_tool
01ToolThis is the only connection the node has. You drag it from the Tool port of a root node, and from then on the agent can call it like any other tool it has been handed.

This is the only connection the node has. You drag it from the Tool port of a root node, and from then on the agent can call it like any other tool it has been handed.

Key parameters

  • Required : the node never executes alone, so the connection to a root node is the thing that makes it exist at all. Nothing upstream plugs into it.
  • AI Agent : the usual host, and the one the documentation example is built around.
  • AI Agent Tool : an agent exposed as a tool to another agent, which can carry its own thinking step.
  • MCP Server Trigger : accepts it too, when the tools you expose over MCP include a reflection step.
Use cases
one agent, several tools, and a decision about which to call. That is where the Tool port earns the extra connection.
Parameters

What goes in the node's one parameter?

The Think Tool node has one parameter. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

01

Think Tool Description

description

What you see in n8n

Notes & use cases

The description is what the agent reads to decide whether calling this tool is worth it. n8n passes it to the model alongside the other tool descriptions, so vague text leaves the tool unused.

Key parameters

  • Think Tool Description : a required string, described in the node as the thinking tool's description. Leave it empty and the node blocks the run. The placeholder spells out the brief, [Describe your thinking tool here, explaining how it will help the AI think], and an expression such as {{ $json.description }} feeds it from the incoming item.
Use cases
tell the agent when to think, not how. Naming the trigger, any question that carries more than one condition, works better than a generic invitation to reflect.
Need help

Need help automating Think Tool with n8n?

A person reads every message.

FAQ

Think Tool in n8n, the questions that come next

01Is the Think Tool node included in n8n, on Cloud and self-hosted?
Yes. It ships inside n8n's AI package, so there is nothing to install and nothing extra to pay on the n8n side, whether you run n8n Cloud, the hosted offer, or you self-host with Docker or npm under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both setups. The only cost attached to a thinking step sits with the model provider: the chat model you plugged into the root node handles the reasoning, and that provider bills its own API calls under its own terms. n8n adds nothing on top of them.
02What do you need to make the n8n Think Tool node work?
Nothing to authenticate, which is unusual enough to be worth saying plainly. The node has no credential and no Authentication selector, because it never talks to an outside service. The credential lives one node away, on the chat model sub-node you wired into the root node, and that is the account the provider checks. So the checklist is short: a root node that offers a Tool port, this node dragged onto it, a chat model attached to that same root node with its own key, and the description filled in. There is no account to create for the Think Tool itself.
03What are the limits of the Think Tool node?
It has no main input and never runs on its own, so it cannot sit in the middle of a workflow like a regular node. It fetches nothing, calls no API, and touches no external system, which means it cannot verify a fact: it only gives the model room to reason with what it already has. At version 1 it exposes a single parameter, so there is no way to cap how long the thinking runs or to force a format on it. And the reasoning is not free for the model provider, since every reflection is more tokens on the chat model attached to the root node.
04What should you connect at a minimum, and which sub-node is best to start with?
At a minimum: a root node that exposes a Tool port, a chat model sub-node so the agent can produce text at all, and this node on that Tool port. The usual starting point is an AI Agent with an OpenAI or Anthropic chat model attached, then Think Tool added once the agent starts picking between several actions. Start without it, watch a few runs, and add it when you see the agent commit too early. An agent exposed through AI Agent Tool, or a set of tools published by an MCP Server Trigger, can carry it the same way.
05n8n or Make for an agent that needs to reason?
It depends on what matters to you. Make runs hosted only, with no self-hosting option, and bills per operation, so a chatty agent that calls a thinking step on every question shows up directly in the bill. n8n runs on your own server or on n8n Cloud, with the same workflow either way, and the sub-node model puts the reasoning step on a port you can see and unplug. If your team wants data staying on infrastructure it controls, that pushes toward n8n. If nobody wants to touch a server, hosted wins. Both build visually, so judge on hosting, data control and cost model.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations