Check CAPTCHA Node
Browser NodePassive observer for the auto-CAPTCHA flow. Detects whether a CAPTCHA widget is on the page and waits for the background auto-solver to finish before continuing.
When to use this node
Use Check CAPTCHA when Auto-CAPTCHA is ON in your Cloud Browser settings (it's on by default). Prompteryx's runtime quietly solves any reCAPTCHA v2, hCaptcha, or Cloudflare Turnstile widget it sees on a page, but that solve runs asynchronously — if your workflow tries to click "Submit" right after the CAPTCHA appears, it can race the solver and submit an empty form.
This node fixes that race. Drop it in just before any form-submit step that follows a page with a CAPTCHA. It waits for a valid token to appear in the page's hidden response field, then succeeds; downstream nodes then run knowing the solve is done.
On your own Chrome (through Prompteryx Desktop), the same setting makes Prompteryx solve a CAPTCHA right after each Open Page navigation, before the next node runs. There is no background solver there for a CAPTCHA that appears later (for example after a click) — use Solve CAPTCHA for those.
Does NOT spend a CAPTCHA solve
Parameters
When CAPTCHA found but unsolvedwait → block this node until a token appears or the timeout hits (recommended). fail → throw an error so the workflow branches via the failed-node handler. continue → succeed anyway; downstream logic inspects the boolean outputs.
waitWait timeout (ms)Only used in 'wait' mode. 2Captcha solves take 20–60s; on the cloud, allow extra time for the background auto-solver to pick the CAPTCHA up. The node exits early as soon as a token is detected, so a generous timeout is free if it isn't needed.
120000Detected flag variableVariable name to store the 'was a CAPTCHA present?' boolean.
captchaDetectedSolved flag variableVariable name to store the 'did the auto-solver inject a valid token?' boolean.
captchaSolvedOutputs
detected: boolean — was a supported CAPTCHA widget on the page?
solved: boolean — has the auto-solver injected a token recently?
type: 'recaptcha' | 'hcaptcha' | 'turnstile' | null
waitedMs: number — wall-clock spent in this node
No visual confirmation on the page
The CAPTCHA widget never shows a green tick
When a token is injected programmatically (which is how all third-party CAPTCHA solvers work, including ours), the reCAPTCHA / hCaptcha / Turnstile widget does NOT update its visual state — no green checkmark, no "verified" label. The token is written directly to the hidden form field that the page reads on submit.
This is normal and expected. To confirm a solve, look at the node's output (solved: true) or perform the form submit and observe whether the server accepts it. The page UI is not a reliable indicator.
Typical workflow
- Open Page → navigate to the form (auto-CAPTCHA fires in the background).
- Fill → first name, last name, email, etc.
- Check CAPTCHA → wait for the auto-solver to put a token in
g-recaptcha-response. - Click → press the submit button. By the time this runs, the token is in place.
Why does this sometimes take 60–90 seconds?
2Captcha-bound, not Prompteryx-bound
The wait time is determined almost entirely by the upstream solver. 2Captcha (the third-party human-in-the-loop solver Prompteryx routes through) typically returns a reCAPTCHA v2 solution in 20–60 seconds. On top of that, the cloud auto-CAPTCHA loop has its own polling interval before it picks up a freshly-rendered CAPTCHA — total wall-clock can land at 60–90s in normal operation.
If you need predictable timing (e.g. you're measuring workflow latency for SLAs), use Solve CAPTCHA instead. It synchronously calls the solver from the current step rather than waiting for the background loop.