Skip to main content
StealthGPT ships an official, n8n-verified node, n8n-nodes-stealthgpt — listed on the n8n integrations directory. You can start full content-pipeline runs and humanize text directly from your n8n workflows. It uses the async API under the hood (start a run, then wait for completion or poll), which fits n8n’s long-running execution model.
This is a verified node, so it’s available on both self-hosted n8n and n8n Cloud. An instance owner enables it once (see Install); after that everyone on the instance can use it in their workflows.

​
Install

1

Open community nodes (instance owner)

In n8n, go to Settings → Community nodes → Install.
2

Install the verified node

Enter the package name and install:
n8n-nodes-stealthgpt
As a verified node it installs cleanly on self-hosted and n8n Cloud.
3

Find the node

Add a new node and search for StealthGPT — it appears in the nodes panel for everyone on the instance.
Only an instance owner needs to do this one-time install. See n8n’s guide on using verified community nodes.

​
Credentials

Create a StealthGPT API credential:
  1. Add the StealthGPT node to a workflow and create a new credential when prompted.
  2. Paste your API token from the Stealth API dashboard.
  3. Save — n8n validates the token against your account balance.
Your API token lives only in your n8n credential store. It is never embedded in the node package.

​
Operations

The node exposes two resources:
ResourceOperationWhat it does
Content GenerationStart RunStart a full Stealth Agent run (research → draft → optional fact-check → humanize → optional images). Inputs: preset (academic | seo | social), prompt, platform (for social), enableFactCheck, enableImageGeneration.
Content GenerationGet Run StatusRetrieve the status and result of a content generation run by runId.
Text HumanizationStart RunTurn existing text into natural, human, publish-ready content. Inputs: text, qualityMode (fast | quality), model (heavy | lite), outputFormat (text | markdown).
Text HumanizationGet Run StatusRetrieve the status and result of a humanization run by runId.

​
Wait for completion

Both Start Run operations include a Wait for completion toggle:
  • On (default): the node starts the run and polls until it reaches a terminal state (completed, failed, or cancelled), then outputs the final result. Tune the poll interval and max wait time in the node options for long pipeline runs.
  • Off: the node returns the runId and statusUrl immediately, so you can continue the workflow and check the run later with Get Run Status (useful with n8n’s Wait node or a scheduled poll).
On a completed humanization, howLikelyToBeDetected is a 0–100 human-likeness score where higher is better (more human, less likely to be flagged as AI).

​
Example workflows

  • RSS → SEO article → CMS draft: RSS Trigger → StealthGPT (Content Generation, seo) → your CMS/WordPress node to create a draft.
  • Webhook → Humanize → Docs/Slack: Webhook → StealthGPT (Text Humanization) → Google Docs / Slack.
  • Airtable brief → generate → store: Airtable Trigger → StealthGPT (Content Generation) → write the result back to Airtable.

​
Notes & limits

  • Runs are billed to the account that owns the API token, using standard word-based billing — identical to the REST API and MCP server.
  • Full academic/seo pipeline runs can take a few minutes; humanize-only runs are faster. Because the API is async, prefer Wait for completion (or start + poll) over blocking the whole workflow on one request.
  • For the underlying REST contract, see the async humanization runs and Stealth Agent async runs pages.