Connect n8n to ChatGPT. For your whole team.

Masked for every role: guest names and emails, phone numbers, payment details in reservation rows.

You set this once. Every ChatGPT user in your team gets exactly this.

1. 1

   Install the node

   In n8n, Settings → Community nodes → Install, package @loopthink/n8n-nodes-loopthink. It adds two nodes: the loopthink Runner trigger and the loopthink node that answers.

2. 2

   Create the server in Loopthink

   Pick n8n as the connection. It asks for nothing else: passwords, API keys and the address of any internal system stay on your side.

   

3. 3

   Describe the tool

   Name it, say what it returns, and declare the parameters a model may pass. Here that is two optional bounds, booked_at_min and booked_at_max. The descriptions matter: they are what the model reads to decide what to send.

   

4. 4

   Add a runner and connect it

   Under Runners, add a pull runner. You get four values; paste them into the loopthink Runner credential in n8n. The secret is shown once.

   

5. 5

   Build the workflow

   Three nodes. The trigger claims a call, the Data Table node reads, and Send Result masks the rows and sends them back. Activate it, and the runner shows online within a minute.

   

6. 6

   Wire the filters

   The Data Table node wants its conditions decided up front, so every row exists on every call, whether or not the model filled it. Loopthink sends a ready value for each one under $json.params, under the name you gave the parameter. Pick the column, pick the comparison once, and read the value.

   

{
  "tool": "reservations_search",
  "params": {
    "booked_at_min": "2026-04-01T00:00:00.000Z",
    "booked_at_max": "2026-04-30T00:00:00.000Z"
  }
}

A Postgres database wired into n8n

Swap the Data Table node for a Postgres node. The connection already exists in your n8n, with its own credential, and it stays there. You can let the workflow build the query from $json.params, or write the statement in Loopthink as a fixed value, a parameter the model never sees and cannot replace:

SELECT id, guest, total
FROM reservations
WHERE country = :country
ORDER BY booked_at DESC
LIMIT 50

The :country is filled from what the model passed, escaped by declared type before it leaves us, so the statement arrives ready to run. The database password is never anywhere near us.

An internal API, called from n8n

Same idea, one node further. Put the path in the tool as a fixed value and let an HTTP Request node in your workflow make the call:

URL: http://pms.internal:8080{{ $json.params.path }}

Authentication is the HTTP node’s own n8n credential. Loopthink says what to reach, never what to reach it with, and the host name is one that only resolves inside your network anyway.

1. 01

   Identify

   OIDC/SSO against your own IdP, including Microsoft Entra. The call runs as the person who made it, never as a shared service account.

2. 02

   Authorize

   Per-role, per-tool, read or write. Anything not explicitly granted never shows up in the tool list in the first place.

3. 03

   Mask

   Field-level masking and pseudonymization applied on your side, before the result travels. The model never sees the raw field. Composio, AnythingMCP and both provider tunnels have no field-level masking at all.

4. 04

   Log

   Who asked, which tool, which records, which fields were masked. One audit trail across every AI client, exportable for review.

Native n8n connector: n8n's MCP Server Trigger with one bearer token per workflow, or the instance-level MCP server signed in as one user. An inbound URL on your n8n, and the same rights for everyone who holds the token.

¹ MintMCP, MCP Manager, Pomerium

Coming from one of them? Composio alternative · MintMCP alternative · MCP Manager alternative · AnythingMCP alternative

Does every team member need their own n8n account?

No. Your n8n is the only thing that talks to your systems, and it keeps its own credentials. Your people sign in to Loopthink with their own identity, and every call to a workflow is logged under their name. n8n seats stay where they are today.

Who has to add the connector in ChatGPT?

One person with the right to add connectors in your ChatGPT workspace, once. After that every team member enables it for themselves. Nobody pastes a key, nobody edits a config file.

Where does the n8n key live?

There is none. The runner credential in n8n, four values shown once, lets your n8n pull calls from Loopthink. Database passwords and API keys stay on the n8n nodes that use them, and nothing reaches Loopthink or ChatGPT.

Can somebody write to n8n from the chat?

Not unless you switch it on. Write actions are a separate row in the permission matrix and are off for every role by default. If a role needs one write tool, you grant that one tool to that one role.

What does the model see?

The result of the tool call, after masking. Fields you mark as personal, such as emails, names or card details, are masked before the answer travels to ChatGPT. The model gets the numbers, not the people.

Is there an audit trail?

Yes. Who asked, which tool, which parameters, which fields were masked, when. One log across every client your team uses, exportable for review.

What does it cost?

Free for one person and your own MCP server, forever. Team starts at €99 per month and covers the built connector, per-person identity, roles, masking and audit for the whole team. Prices are on the pricing page, no call needed.

We already run our own MCP server for n8n. Does it still work?

Yes. Point it at Loopthink and it inherits the same login, roles, masking and audit. Nothing on the server has to change.