n8n-nodes-2captcha-official
v1.0.16
Published
Official n8n node to bypass captchas natively using 2Captcha API
Maintainers
Readme
n8n-nodes-2captcha
An n8n community node to automate solving and bypassing the most complex captchas using the 2Captcha.com API.
Designed for web scraping, automation experts, and developers dealing with strict anti-bot systems. The node handles the full submit/poll cycle under the hood — pass the target parameters and get the bypass token back in a single node.
Features
The node has a dynamic UI: pick a captcha type and only the fields required for that type are shown.
Currently supported:
- Cloudflare Turnstile
- reCAPTCHA v2
- reCAPTCHA v3
- reCAPTCHA Enterprise
- Normal Captcha (Image-to-Text via Base64)
No need to build complex Wait or HTTP Request loops — task creation and result polling are handled automatically.
Prerequisites
- An active n8n installation (self-hosted or Cloud).
- A 2Captcha account and an API key. Get one by registering at 2Captcha.
Installation
Install directly from the n8n UI:
- Go to Settings → Community Nodes.
- Click Install.
- Enter
n8n-nodes-2captcha-officialas the package name. - Accept the risks prompt and click Install.
For Docker-based installations you can also add the package to your package.json or install it via the terminal inside the n8n container.
Credentials
- In your workflow, add the 2Captcha node.
- Open the Credential dropdown and choose Create New.
- Paste your 2Captcha API key and save.
The credential is verified against POST https://api.2captcha.com/getBalance, so a successful save also confirms the key works and the account has balance.
Usage
- Select a Captcha Type (Turnstile, reCAPTCHA v2/v3/Enterprise, or Normal).
- Fill in the dynamic fields:
- Token-based captchas need Page URL and Site Key / App ID.
- reCAPTCHA v3 and Enterprise also accept an Action (and v3 accepts Min Score).
- Normal captcha requires the image as a Base64 string.
- Run the node. The solved token is returned on the
tokenfield of the output JSON, ready to be plugged into a subsequent HTTP Request, Puppeteer/Playwright step, or any other node.
Example output
{
"success": true,
"taskId": "7392817492",
"token": "0.xxxxx_valid_bypass_token_xxxxx",
"type": "turnstile"
}