Solve Recaptcha v3

Solves Google reCAPTCHA v3 challenges with score control and returns a response token. reCAPTCHA v3 is Google's invisible captcha that uses behavioral analysis to assess user interactions without requiring user interaction.

Common Properties

• Name - The custom name of the node.
• Color - The custom color of the node.
• Delay Before (sec) - Waits in seconds before executing the node.
• Delay After (sec) - Waits in seconds after executing node.
• Continue On Error - Automation will continue regardless of any error. The default value is false.

info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs

• Session - The session ID returned from the Create Session node.
• Website URL - The full URL of the target page where the reCAPTCHA v3 is active (e.g., https://example.com/checkout).
• Website Key - The site key found in the page source. Format: 6Le-wvkSAAAAAPBMRTvw0Q4M....

Options

• Page Action - The action name for this request (e.g., verify, submit, login, homepage). This should match the action parameter used in the website's reCAPTCHA implementation.
• Min Score - Minimum score required (0.1 to 0.9). Higher values are more strict. Default is 0.3. Google scores range from 0.0 (likely bot) to 1.0 (likely human).
• No Cache - Disable result caching for this task. Default is false. Set to true to force a fresh solve.

Output

• Token - The g-recaptcha-response token to submit with your form or API request.

How It Works

The Solve Recaptcha v3 node solves Google's invisible reCAPTCHA v3. When executed, it:

1. Retrieves the session using the provided session ID
2. Creates a reCAPTCHA v3 solving task with the website URL and site key
3. Optionally adds the page action parameter
4. Optionally sets the minimum score requirement
5. Sends the task to CapMonster Cloud for processing
6. Returns a token with the requested score level

Requirements

• A valid CapMonster session (from Create Session node)
• The full URL where the reCAPTCHA v3 is active
• The reCAPTCHA v3 site key from the page source
• Sufficient account balance
• Active internet connection

Error Handling

The node will fail in the following cases:

• Missing or invalid session ID
• Session not found
• Empty or invalid website URL
• Empty or invalid site key
• Invalid min score value (must be 0.1-0.9)
• Insufficient account balance
• Network connectivity issues
• Captcha solving timeout
• Unable to achieve requested score

Understanding reCAPTCHA v3 Scores

reCAPTCHA v3 returns a score for each request:

• 0.9-1.0: Very likely a human, low risk
• 0.7-0.8: Likely a human, medium-low risk
• 0.5-0.6: Uncertain, medium risk
• 0.3-0.4: Possibly a bot, medium-high risk
• 0.0-0.2: Very likely a bot, high risk

Websites typically set their own threshold (commonly 0.5). The Min Score option lets you request a specific minimum score.

Finding reCAPTCHA v3 Parameters

To find the required parameters, inspect the page source:

Website URL

Use the full URL of the page where the captcha is active:

https://example.com/checkout

Site Key

Look for the reCAPTCHA v3 initialization in JavaScript:

grecaptcha.ready(function() {
    grecaptcha.execute('6Le-wvkSAAAAAPBMRTvw0Q4Muexq5bi0DJwx_mJ-', {
        action: 'submit'
    })
});

Or in the page head:

<script src="https://www.google.com/recaptcha/api.js?render=6Le-wvkSAAAAAPBMRTvw0Q4M..."></script>

Page Action

The action parameter in the execute call:

grecaptcha.execute('site-key', {action: 'submit'})
                                         ↑
                                   This is the action

Common actions:

• homepage
• login
• submit
• verify
• checkout
• contact

Usage Notes

• reCAPTCHA v3 solving typically takes 10-20 seconds
• The response token is valid for approximately 2 minutes
• Higher min scores take longer to achieve and may cost more
• The token includes the score information
• v3 is completely invisible to users
• The page action should match what the website expects

Example: Solving reCAPTCHA v3 on Contact Form

Inputs:

• Session: (from Create Session node)
• Website URL: https://example.com/contact
• Website Key: 6Le-wvkSAAAAAPBMRTvw0Q4Muexq5bi0DJwx_mJ-

Options:

• Page Action: submit
• Min Score: 0.7
• No Cache: false

Output:

• Token: "03AGdBq26Rs5Cv..."

Example: Complete Flow

Create Session (API Key)
  → Browser: Navigate to page
    → Browser: Fill form fields
      → Find site key in page source
        → Solve Recaptcha v3 (action: submit, min score: 0.7)
          → Browser: Execute Script (call grecaptcha with token)
            → Browser: Click submit button

Submitting the Token

reCAPTCHA v3 submission is different from v2. You typically need to execute JavaScript:

Method 1: Set Token and Submit

// Set the token in the hidden field
document.getElementById('g-recaptcha-response').value = token;
// Submit the form
document.querySelector('form').submit();

Method 2: Execute with Token

// Some sites expect you to call grecaptcha.execute with the token
grecaptcha.ready(function() {
    // Your token replaces the need to call execute
    document.getElementById('g-recaptcha-response').value = token;
    submitForm();
});

Method 3: API Request with Token

{
  "name": "John Doe",
  "email": "john@example.com",
  "message": "Hello",
  "g-recaptcha-response": "token_here"
}

Method 4: Callback Function

function onSubmit(token) {
    // This function is called when reCAPTCHA v3 completes
    // Your automation provides the token directly
    document.querySelector('form').submit();
}

Best Practices

• Always specify the correct page action
• Start with a min score of 0.3-0.5 for better success rates
• Increase min score only if the website requires it
• Monitor solve times when using high min scores (0.7+)
• Cache tokens when possible (No Cache = false)
• Verify the site key is for v3, not v2
• Test the action parameter matches the website's expectation
• Handle score requirements dynamically based on site needs

Common Issues and Solutions

Issue: Token rejected by website

• Solution: Verify the page action matches the website's implementation
• Solution: Check if you're using the correct v3 site key
• Solution: Ensure the Website URL matches exactly
• Solution: Try without specifying min score

Issue: "Cannot achieve requested score"

• Solution: Lower the Min Score requirement
• Solution: Check if CapMonster Cloud is experiencing issues
• Solution: Verify your account has sufficient balance
• Solution: Try with No Cache = true

Issue: Wrong captcha version error

• Solution: Verify you're using a v3 site key, not v2
• Solution: Check the grecaptcha.execute call in the page source
• Solution: Look for api.js?render= instead of api2/anchor

Issue: Invalid action parameter

• Solution: Use lowercase action names
• Solution: Match the exact action string from the website
• Solution: Try common actions: homepage, submit, login
• Solution: Leave action empty if unsure

Issue: Token format unexpected

• Solution: v3 tokens are similar to v2 but have different internals
• Solution: Don't parse or modify the token
• Solution: Submit the entire token as-is

Choosing the Right Min Score

Different use cases require different score thresholds:

Low Security (0.1-0.3)

• Public contact forms
• Newsletter signups
• Non-critical actions
• Faster solving
• Lower cost

Medium Security (0.4-0.6)

• Account registration
• Comment posting
• General form submissions
• Balanced approach
• Moderate solving time

High Security (0.7-0.9)

• Financial transactions
• Sensitive data submission
• High-value actions
• Slower solving
• Higher cost
• May fail more often

Page Action Best Practices

• Use descriptive actions: login instead of l or 1
• Match the website: Extract the action from the page source
• Be consistent: Use the same action for the same operation
• Common patterns:
  • Homepage visits: homepage
  • Form submissions: submit
  • User authentication: login
  • Checkout process: checkout
  • Account creation: signup

reCAPTCHA v3 vs v2

Feature	v2	v3
User Interaction	Required (checkbox/images)	None (invisible)
Score	Not applicable	0.0 - 1.0
Action Parameter	No	Yes
Solve Time	15-40 seconds	10-20 seconds
Implementation	Explicit widget	JavaScript execute
User Experience	Disruptive	Seamless

Cost Considerations

• reCAPTCHA v3 solving costs are typically lower than v2
• Higher min score requirements may increase cost
• Check CapMonster Cloud pricing for current rates
• Use caching (No Cache = false) for cost efficiency
• Balance between score requirements and budget

Advanced Tips

• v3 can coexist with v2 on the same page (different site keys)
• Some sites use v3 as a pre-filter and fall back to v2 if score is low
• Token format starts with 03 like v2 but has different payload
• Google may return different scores based on IP reputation
• Action parameter is case-sensitive (use lowercase)
• Multiple actions can exist on the same page
• Always verify the token immediately; don't store for later use
• Consider implementing a score fallback strategy (try 0.5, then 0.3, etc.)