--- title: "OpenThesaurus Integration" description: "Look up German-language synonyms using the free, public OpenThesaurus thesaurus. Results group into synonym sets, with optional phonetically similar words, substring and prefix matches, hyponyms, hypernyms, and base forms. No authentication required." url: https://flowrunner.ai/integrations/openthesaurus date_modified: 2026-08-07T17:20:23-07:00 --- # OpenThesaurus [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Look up German-language synonyms using the free, public OpenThesaurus thesaurus. Results group into synonym sets, with optional phonetically similar words, substring and prefix matches, hyponyms, hypernyms, and base forms. No authentication required. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 action · API key · available [OpenThesaurus website](https://openthesaurus.de/) · [Platform Documentation](https://www.openthesaurus.de) · Capability data verified 2026-08-12 1. A German copy draft enters an editing workflow 2. Agent calls Get Synonyms for each flagged repetitive term 3. Agent reads the synonym sets returned for each word 4. Agent filters synonyms that fit the register and context 5. Agent assembles the proposed wording changes in context 6. Agent presents the before-and-after copy for review 7. Any change to published German copy waits for an editor's approval ## What This Integration Enables The OpenThesaurus connector lets agents pull German synonyms inside a content workflow. Get Synonyms takes a word plus optional flags for phonetically similar words, substring matches, prefix matches, hyponyms, hypernyms, and base forms, so the agent can widen or narrow the result set to fit the task. Unknown words return an empty synonym set rather than an error, which lets a workflow probe freely. Because it is read-only and keyless, the connector adds no configuration burden; it supplies candidate words, and the surrounding flow decides which ones a human should see. ### Without FlowRunner **Synonyms looked up by hand**: A writer opens a thesaurus tab and searches word by word **Repetition slips through**: Repeated German terms survive because checking each one is tedious **No consistent vocabulary**: Related terms are chosen ad hoc across a document ### With FlowRunner **Synonyms pulled inline**: The agent looks up alternatives for flagged terms during editing **Repetition surfaced**: Repeated words become suggestions with fitting alternatives attached **A reviewable vocabulary**: Proposed changes arrive in context for a person to accept or reject ## Use Case Scenarios ### German Copy Variation An editing agent processes German drafts. It detects repeated terms, calls Get Synonyms for each, and proposes fitting alternatives to vary the phrasing. Because the agent can feed synonym groups into a rewriting step, it suggests wording rather than mechanically swapping words. The suggestions arrive in context so a person keeps control of tone. ### Typo Correction Suggestions A workflow processes user-submitted German text. For likely typos, the agent calls Get Synonyms with the Similar Words flag enabled to return phonetically close terms, then suggests the most plausible correction. The Levenshtein-based matches give the agent a shortlist rather than a single guess, which keeps a human in the decision on ambiguous corrections. ### Search and Tagging Vocabulary A team wants richer search and tagging for German content. The agent pulls related terms for each keyword with Get Synonyms, optionally including hyponyms and hypernyms, and builds an expanded vocabulary. The expanded set improves recall without a person hand-listing every related word. ## Human-in-Loop Highlight Looking up a synonym is harmless. Swapping a word in published German copy is an editorial decision, and the agent does not make it silently. The connector only reads the thesaurus, so the agent gathers candidates freely, but the moment a synonym would change customer-facing text, it stops. When the agent proposes replacing a repeated term, it presents the change in context and routes to the editor through their channel: "In the pricing section, 'guenstig' appears three times. I can vary it with 'preiswert' or 'erschwinglich'. Apply the changes, or leave the copy as written?" This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) at the seam where a lookup becomes a published edit: the agent handles the research, and a person owns the voice. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 1 actions ### Thesaurus 1 - **Get Synonyms** Look up German synonym sets for a word, with optional similar words, substring, prefix, sub-synset, super-synset, and base-form flags. Each flag defaults to off and is applied only when enabled. Use it to vary phrasing, suggest typo corrections, or expand a vocabulary. ## Frequently Asked Questions ### What can FlowRunner do with OpenThesaurus? FlowRunner agents can run Get Synonyms in OpenThesaurus. ### Does connecting OpenThesaurus to FlowRunner require OAuth? No. OpenThesaurus connects to FlowRunner with an API key, no OAuth flow required. ### Can OpenThesaurus trigger a FlowRunner workflow automatically? OpenThesaurus doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at OpenThesaurus?** This integration exposes OpenThesaurus to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/openthesaurus. Site index: https://flowrunner.ai/llms.txt