Resources · n8n integration

OpenThesaurus n8n integrationAutomate OpenThesaurus with n8n.

Rewriting the same German sentence three times gets old fast. The OpenThesaurus n8n integration exposes 1 operation that looks up synonyms for a German word, plus 8 options that widen or tighten what comes back. No credential to create, no trigger node: a Schedule or Webhook step starts the run.

Try the OpenThesaurus integration on n8nSee the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the OpenThesaurus n8n integration actually give you?

OpenThesaurus is a German thesaurus. The n8n node asks it about one German word and hands back the synonym groups it knows, so a workflow can find another way to say something without a person in the loop. The whole node is one operation, Get synonyms, and it ships inside n8n on Cloud and on a self-hosted instance alike. Nothing to install, nothing extra to pay on the n8n side.

The clearest use is a vocabulary column that fills itself. A German word lands in a Google Sheets row, the node reads that cell into its Text field, and the synonym groups come back for the next node to write into a second column. What used to be a glossary someone maintained by hand becomes an output of the workflow.

The second use is variation before a human reads anything. A German product title or ad line goes through the node, the alternatives get collected, and the shortlist drops into Slack for the person who signs off. They pick instead of inventing, which is a much faster job.

The third use is search terms. Customers rarely type the word that sits in your catalog, so a nightly run can take each German product term, pull its synonym groups, and store them as alternative labels for your own search index. Turn Substring on for that job and partial-word hits come back too, which catches the compound forms German is full of.

One thing to keep straight: the node speaks German, and only German. If the text you start from is in another language, translate it first with DeepL or Google Translate, then feed the German result into Text. Chaining those two nodes is a five-minute job and it keeps each node doing what it is good at.

If you need something the node's operation does not offer, the HTTP Request node calls any endpoint of the tool's API directly, which is the standard escape hatch in n8n. And because there is no OpenThesaurus trigger node, every workflow here starts elsewhere: a Schedule Trigger at a fixed interval, an n8n Webhook that a third-party service calls, or the trigger of another tool you already use. If you want the pattern explained end to end, that is the kind of thing covered in the n8n training.

Connect

How do you set the node up?

  1. 01

    Pick what starts the workflow

    OpenThesaurus has no trigger node of its own, so the first block on your canvas is something else. A Schedule Trigger fires at a fixed interval, which suits a nightly pass over a word list. An n8n Webhook gives you a URL that a third-party service calls when it has a word to enrich. Or you reuse the trigger of a tool already in the workflow, such as a new row in a spreadsheet.

  2. 02

    Drop in the node and move on

    Add the OpenThesaurus node after your trigger. There is no credential to fill in, because the node does not require authentication. A credential in n8n is the saved login you create once under the Credentials menu and reuse in every workflow; here you simply skip that step. It is one of the rare nodes you can wire up and run in the same minute.

  3. 03

    Map Text and run once

    The Text field holds the German word to look up. Type one in while you are testing, then swap it for an expression once the workflow is live. An expression is the n8n syntax that reads a value from the item coming in, written {{ $json.field }}. Text is required, so an empty value stops the node instead of returning nothing, which is the behavior you want.

Actions

What the node does

The OpenThesaurus node exposes one operation. For each one: the node as you configure it in n8n, the required fields, and our field notes.

01

Get synonyms

getSynonyms

What you see in n8n

Notes & use cases

Looks up one German word and returns the synonym groups OpenThesaurus holds for it, ready for the next node.

Key parameters

  • Text: the German word to look up. Required, and usually an expression such as {{ $json.field }} pointing at the column or payload the word arrived in.
  • Baseform: gives the base form of the search term when what you sent is not one already, which saves you from normalizing words yourself.
  • Similar: also returns up to five similarly written words per answer, so you can suggest a correction when someone mistyped.
Use cases
enrich a German glossary row by row, or widen one product term into the handful of words your customers actually search for.
Need help

Need help automating OpenThesaurus with n8n?

A person reads every message.

FAQ

Questions people ask next

01Is the OpenThesaurus n8n integration free to use?
On the n8n side, yes. The node ships with n8n, so there is nothing to install from a marketplace and no extra fee for using it. That holds on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, so you can prototype on Cloud and move it to your own server later without rewriting anything. What the tool itself costs is a separate question and not one this page answers.
02What credentials does the OpenThesaurus node need?
None. The node does not require authentication, so there is no API key to generate, no account to link, and no Credentials entry to create before your first run. For most n8n nodes you build a credential once under the Credentials menu and then pick it from a dropdown in every workflow that needs it. Here that dropdown step simply is not there. The practical effect is that the gap between adding the node and seeing real output is about as short as it gets, which makes this a decent node to learn expressions on.
03What are the limits of the OpenThesaurus node in n8n?
The node is built around a single operation, Get synonyms, which takes one German word in the Text field. The 8 options shape what comes back: Baseform, Similar, Starts With, Substring, Substring From Results, Substring Max Results, Subsynsets and Supersynsets. If what you need is not among the node's operations, the HTTP Request node calls any endpoint of the tool's API directly, which is the normal fallback in n8n and keeps the rest of your workflow untouched. Plan for one word per execution and loop over your list rather than expecting a batch call.
04Does OpenThesaurus have a trigger node in n8n?
No. There is no OpenThesaurus trigger, so nothing on the OpenThesaurus side can start a workflow. You start it yourself with one of three things. A Schedule Trigger runs at a fixed interval, which fits a nightly pass over a vocabulary sheet. An n8n Webhook gives you a URL that another service calls when it has a word ready, so the run happens when the event happens. Or the workflow begins with the trigger of a tool you already use, such as a new row or a new message, and the OpenThesaurus node sits further down the chain.
05n8n or Make for a German synonym lookup?
It comes down to four things. Hosting: n8n runs on your own server with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control: on a self-hosted n8n the words you look up and the results never leave your machine, which matters if the source text is customer content. Cost model: Make bills per operation, so a loop over a long word list is a line item there and a runtime question on n8n. Visual logic: both draw the flow on a canvas, and the choice between them is mostly a matter of what your team already reads fluently. Neither is wrong for this job.
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