> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stealthgpt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate StealthGPT with n8n

> Generate long-form content and humanize text inside n8n workflows with the StealthGPT community node

StealthGPT ships an official, **n8n-verified** node, [`n8n-nodes-stealthgpt`](https://www.npmjs.com/package/n8n-nodes-stealthgpt) — listed on the [n8n integrations directory](https://n8n.io/integrations/stealthgpt/). 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.

<Info>
  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.
</Info>

## Install

<Steps>
  <Step title="Open community nodes (instance owner)">
    In n8n, go to **Settings → Community nodes → Install**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Find the node">
    Add a new node and search for **StealthGPT** — it appears in the nodes panel for everyone on the instance.
  </Step>
</Steps>

<Note>
  Only an instance owner needs to do this one-time install. See n8n's guide on [using verified community nodes](https://n8n.io/integrations/stealthgpt/).
</Note>

## 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](https://stealthgpt.ai/stealthapi/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:

| Resource               | Operation      | What it does                                                                                                                                                                                                                               |
| ---------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Content Generation** | Start Run      | Start 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 Generation** | Get Run Status | Retrieve the status and result of a content generation run by `runId`.                                                                                                                                                                     |
| **Text Humanization**  | Start Run      | Turn existing text into natural, human, publish-ready content. Inputs: `text`, `qualityMode` (`fast` \| `quality`), `model` (`heavy` \| `lite`), `outputFormat` (`text` \| `markdown`).                                                    |
| **Text Humanization**  | Get Run Status | Retrieve 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).

<Note>
  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).
</Note>

## 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](/api-reference/endpoints/stealthify-runs) and [Stealth Agent async runs](/api-reference/endpoints/stealthify-agent-runs) pages.