How to Connect Reepl to n8n
Drive Reepl from self-hosted or cloud n8n workflows using an API key and the HTTP Request node.
n8n is a workflow automation tool you can self-host. Reepl connects to it through its REST API, so any n8n workflow can create drafts, schedule posts, generate carousels, or react to Reepl events.
Before you start: you need a Reepl account on a Pro plan or above, and a Reepl API key. See API keys & scopes for how to create one.
Generate a Reepl API key
Open Settings → Developers
In Reepl, go to Settings → Developers, on the API keys tab.
Connect n8n
Click Connect on the n8n card. Its scopes come pre-ticked with what the integration actually uses: reading and writing drafts and posts, carousels, the AI tools, your profile, and webhooks:manage so triggers can register themselves.
Copy the key
Click Generate Key and copy it straight away — it is shown once and cannot be retrieved later.
Call Reepl from a workflow
n8n has no dedicated Reepl node, so use the HTTP Request node.
Add an HTTP Request node
Set the method and URL for the endpoint you want, for example POST https://api.reepl.io/v1/external/drafts.
Add the authentication header
Under Headers, add X-API-Key with your rpl_live_… key as the value.
Store the key as an n8n credential rather than typing it into the node, so it is not exposed in the workflow JSON when you export or share it.
Send the body as JSON
Set Body Content Type to JSON and shape the body to match the endpoint. The API reference has the schema for each one.
React to Reepl events
To start a workflow from Reepl rather than calling into it:
Add a Webhook node
Add n8n's Webhook node and copy its production URL.
Register it in Reepl
In Settings → Developers → Webhooks, add that URL and tick the events you want.
Verify the signature
Reepl signs every delivery. Check X-Reepl-Webhook-Signature before you trust the payload — the recipe is on the Webhooks page.
Troubleshooting
| Problem | Likely cause |
|---|---|
401 Unauthorized | The key is wrong, disabled, or was regenerated. Check Settings → Developers. |
403 Forbidden naming a scope | The key lacks that scope. Click Manage on the key in Settings → Developers and edit its permissions; the key value stays the same. |
403 with requiresUpgrade | The Reepl subscription is not active. Every endpoint except GET /external/me needs a paid plan. |
| A trigger never fires | Check the webhook subscription is still enabled — Reepl disables one automatically after 10 consecutive delivery failures. See Webhooks. |
Related
How to Connect Reepl to Raycast
Run Reepl actions from Raycast on macOS using an API key and a script command.
How to Connect Reepl via MCP
Connect Reepl to Claude, ChatGPT, OpenClaw, or any other MCP client using the Model Context Protocol to write posts, schedule content, manage carousels, and more through natural language