CaptchaSonicInstall

Summary

Solves an AWS WAF CAPTCHA through the CaptchaSonic API and returns the solved result. It creates a task, then polls every 3 seconds for up to 120 seconds until the task is ready.

Inputs

• Task Type (required) — Either 'AWS WAF (Proxy-Less)' (AntiAwsWafTaskProxyLess, the default) or 'AWS WAF' (AntiAwsWafTask). The non-ProxyLess type needs a proxy.
• Website URL (required) — URL of the page that shows the AWS WAF CAPTCHA.
• Website Key — Sitekey for the CAPTCHA widget. Sent only when it is non-empty.
• Proxy — Proxy as protocol://user:password@host:port. The field description says it is required for non-ProxyLess task types. It is sent only when set.
• User Agent — Browser User-Agent string to use when solving. Sent only when set.
• Optional Fields — Collection of extras. Non-empty values are added to the task. 'Page Action' and 'CData' are nested under task.metadata, and 'Enterprise Payload (JSON)' is parsed as JSON. API Domain, Cookies, Is Invisible and Min Score are also passed through. Most of these are labelled for reCAPTCHA and may not apply to AWS WAF.

Output shape

One item per input item: { success: true, data: }. The response has status 'ready' and contains the solution.

The solution fields inside data are defined by the CaptchaSonic API and not by this node. If the API returns an error, the task fails, or polling times out after 120 seconds, the node throws. With Continue On Fail enabled, it instead outputs { error: message } for that item. Requires the captchaSonicApi credential (API key).

Examples

Example 1: Get an AWS WAF token for a protected page without using a proxy

Task Type: AWS WAF (Proxy-Less); Website URL: https://example.com/protected; Website Key: the site's WAF key.

Example 2: Solve using your own proxy and a fixed browser fingerprint

Task Type: AWS WAF; Website URL set; Proxy: http://user:pass@1.2.3.4:8080; User Agent: a desktop Chrome UA string.

Links

• n8n community nodes installation guide