PrompteryxBeta
    ⌘K
    PlatformSupport
    Menu
    IntroductionInstall Desktop & extensionQuick StartPlatform Overview
    OverviewWhat you can makeAI Browser Agent in the chatModels and AutoConnectorsSchedulesProjectsExplore and publishingShare linksMemory and SkillsPersonal agent (beta)Welcome, settings and skinsPlans, credits and top-upsPrompteryx DesktopGroups (pilot)Phone app (early access)
    OverviewCreating WorkflowsTesting & DebuggingScheduling
    OverviewGetting StartedCommandsRecordingSettingsStructured OutputParallel AgentsTips & Best Practices
    OverviewInstallationSidebar AgentUsing Attached FilesExecute on Current TabExporting to Visual Studio
    Overview
    OverviewOpen PageClickClick CoordinatesFillExtract TextScreenshotWaitPress KeyFocus ElementBlur ElementSelect TextHighlight ElementSet ViewportGet Bounding BoxScrollHoverSelect OptionAssertionsCookiesEvaluate JavaScriptExample Workflows
    OverviewPrompteryx Browser AgentOpenAI
    OverviewSchedule TriggerWebhook Trigger
    OverviewGoogle SheetsGoogle CalendarConnect Hub (3,000+ apps)Example Workflows
    AI Vision SettingsChrome Automation ProfilesCloud BrowserBrowser Profiles & Persistent ContextVideo RecordingExecution LogsSharing & CollaborationEdit History
    Selectors GuideVariables
    Start hereGet an API keyRun the AI browser agentDrive a cloud browserRun workflows from anywhereUse connected apps (Connect Hub)SDK (TypeScript)CLIMCP for AI assistants
    REST APIWebhooksMCP toolsCloud Browser APICloud Browser quickstartMigrate from Browserbasen8nZapierMake.com

    Need help? Contact Support

    1. Documentation
    3. Nodes
    5. Browser Actions
    7. Solve Captcha

    Solve CAPTCHA Node

    Browser Node

    Active solver. Detects the CAPTCHA on the page, calls the solver, and injects the token. Use when you want deterministic timing, or when Auto-CAPTCHA is turned off.

    When to use this node

    Use Solve CAPTCHA when:

    • Auto-CAPTCHA is OFF in your Cloud Browser settings — there's no background solver running, so the workflow needs to solve explicitly.
    • You want deterministic timing. The node runs the solver inline, so the wall-clock for this step is the solve time itself — useful when you're measuring workflow latency.
    • You've disabled auto-solving for cost control but still need to clear a CAPTCHA in one specific workflow.
    SPENDS one CAPTCHA solve per run
    Unlike Check CAPTCHA (which is passive and free), Solve CAPTCHA always bills one solve when a CAPTCHA is on the page — from your plan's monthly CAPTCHA allowance first, then any top-up balance — regardless of whether Auto-CAPTCHA is on. The Solve CAPTCHA node also bypasses the user-level Auto-solve preference — it's explicitly opt-in at the workflow level. The monthly cap + balance check still apply.

    Parameters

    Parameters
    Configuration options for this node
    Solve timeout (ms)
    Number

    2Captcha reCAPTCHA solves typically take 20–60s; 180s covers the long tail. Values below 120000 (2 minutes) are raised to 120000; the maximum is 300000. If the solver times out or rejects the request, the node throws — pair with a failed-node handler if the workflow needs to recover.

    Default: 180000
    Fail if no CAPTCHA detected
    Boolean

    When ON, the node throws if there's no supported CAPTCHA on the page. Useful when the workflow KNOWS a CAPTCHA must be present and absence is itself a bug. Default OFF — the node succeeds as a no-op when the page is clean, which is convenient for loops that run on each click without knowing if a CAPTCHA will appear.

    Default: false
    Solved flag variable
    String

    Variable name for the 'did we get a token and inject it?' boolean.

    Default: captchaSolved
    Token variable
    String

    Variable name to store the solver token. Mostly diagnostic — the token is already injected into the page so downstream form-submit nodes don't need to read it.

    Default: captchaToken

    Outputs

    detected: boolean — was a supported CAPTCHA on the page?

    solved: boolean — did the solver return a token and did we inject it?

    type: 'recaptcha' | 'hcaptcha' | 'turnstile' | null

    skipped: null | 'no-quota' | 'feature-off' | 'no-solver-key' — why the solve didn't run (if it didn't).

    spentMs: number — total wall-clock the node spent.

    No visual confirmation on the page

    The CAPTCHA widget never shows a green tick

    When the solver injects a token programmatically (which is how all third-party solvers work), the reCAPTCHA / hCaptcha / Turnstile widget does NOT update its visual state. You will NOT see a green checkmark or "verified" label on the page. The token is written directly to the hidden form field that the page reads on submit.

    Confirm the solve via the node's output (solved: true) — and by whether the subsequent form-submit step succeeds. The widget UI is not a reliable indicator.

    Typical workflow

    Form on a CAPTCHA-protected page (Auto-CAPTCHA OFF)
    Open → fill → SOLVE → submit
    1. Open Page → navigate to the form.
    2. Fill → first name, last name, email, etc.
    3. Solve CAPTCHA → detects the widget, calls the solver, injects the token (this is where the 20–60s sits).
    4. Click → press the submit button.

    Error scenarios

    CAPTCHA solver not configured on the web app
    The CAPTCHA solving service isn't available on the Prompteryx side right now, so the node can't solve. This isn't caused by your workflow or account, and no solve is charged.
    CAPTCHA solve quota exhausted
    Your monthly CAPTCHA allowance + top-up balance is empty. Buy a CAPTCHA Pack from the subscription page ($2 = 400 solves) or upgrade to a higher tier.
    No CAPTCHA detected on the page
    The page didn't have a supported CAPTCHA widget. This is only an error when "Fail if no CAPTCHA detected" is ON; by default it's a graceful no-op that succeeds.

    Best practices

    Pair with Auto-CAPTCHA off for cost-controlled workflows
    Setting Auto-CAPTCHA off in your Cloud Browser settings + dropping Solve CAPTCHA at precise points gives you fine-grained control over where solves get spent. You only pay for solves you EXPLICITLY want.
    Don't combine with Check CAPTCHA in the same flow
    The two nodes are alternatives, not partners. Check CAPTCHA waits for an existing auto-solve; Solve CAPTCHA performs its own. Running both back-to-back at best wastes one solve, at worst races with itself.
    Wrap in a failed-node handler for critical flows
    The solver occasionally times out. A failed-node handler that retries once or logs to your error stream prevents a single bad solve from dropping a paid signup. Note that a timed-out solve still counts against your allowance (the solver may finish and charge after the node gives up); solves the solver reports as unsolvable are refunded.

    Related Documentation

    Check CAPTCHA Node

    Passive observer — waits for the background auto-solver, no cost

    Cloud Browser

    Auto-CAPTCHA settings + quota