manual_captcha_solve to false. The dashboard no longer offers this setting. Workflows created before manual solving became the default keep their setting; move them to Captcha nodes. See Workflow Settings.
Parameters
Examples
Turnstile before a submit
reCAPTCHA v2
hCaptcha after the site’s own checkbox
Some sites show their own “I am not a robot” checkbox and open the hCaptcha challenge when it is ticked. Click that checkbox first, then solve:AWS WAF CAPTCHA after the site’s own checkbox
Some sites load the AWS WAF puzzle hidden and show it when their own “Let’s confirm you are human” checkbox is ticked. Click that checkbox first, then solve. The same node also clears AWS’s full-page “Human Verification” page; do not click its Begin button, because the node presses it:Text (image transcription)
A distorted-character image with a text input the user must type into. Text captchas are only solved by this node, never automatically, whatevermanual_captcha_solve is. The node reads the challenge and fills the field; do not author a read-and-retype loop of your own.
Custom site challenge
Some sites draw their own challenge, such as “Please enter the number value of each image” over a row of dice, or “Enter the number of bowties shown”, with a text box for the answer. Point the node at the challenge and the answer box. It reads the challenge, types the answer, and stops; add a Click node after it to submit:question_selector:
max_iterations below the number of attempts the site allows.
Notes
- If no captcha of that type is on the page, the node passes and the run continues. Custom is the exception: it does not detect a captcha, so if an XPath matches nothing within
wait_time, the node fails like a Click would - If the captcha is present and cannot be solved, the node fails with error code
CAPTCHA-E0001, so the workflow’s error-code actions (alert, retry, pause_workflow, pause_credential) apply - Do not add a Click on the captcha widget itself. Clicking into a half-solved widget breaks the solver. A Click on the site’s own checkbox that opens the captcha is fine
- Detection finds the widget’s iframe or container in the top page. reCAPTCHA v2 is also found on a page embedded in an iframe from the same site, such as a security check page that shows the captcha inside the site’s own frame. Any other captcha on an embedded page, and any captcha on a page embedded from a different site, is not detected, and the node passes as if no captcha were present
- A
textcaptcha is found by its challenge image and the adjacent text input in the top page; the solver reads the characters and types them, retrying up to twice more (three attempts in all) against its own Submit/Verify control if a read is rejected. When no challenge is showing yet, the node waits up to 15 seconds for one to appear - reCAPTCHA v2 is solved by CloudCruise’s own solver
- hCaptcha is solved by CloudCruise’s own solver. When hCaptcha is on the page but no challenge is showing yet, the node waits up to 15 seconds for one to open, and passes as soon as the widget has a token
- AWS WAF CAPTCHA is solved by CloudCruise’s own solver, both as a puzzle inside the site’s page and as AWS’s full-page “Human Verification” check with a Begin button. When the puzzle is on the page but not showing yet, the node waits up to 15 seconds for it to appear
- With automatic solving on, the node still runs, and is a fast no-op once the captcha is already solved. Automatic solving only acts on a challenge that is already open when a step starts, so a captcha that a site opens from its own checkbox or button still needs a Captcha node right after that click
- Custom reads the challenge element only, types the answer into the answer box, and does not submit. Custom challenges must be on the page itself or in a frame from the same site