A Dagster CAPTCHA step is one op with a retry policy, and the token must never cross an op boundary. The default IO manager pickles outputs to disk, which is the wrong place for a single use credential.

TestCafe test code runs in Node, so you call the solver directly and write the token in with a ClientFunction. Check native automation is on first, because the legacy proxy breaks reCAPTCHA before a solver is involved.

Three HTTP modules and a Sleep, no code step anywhere. The one thing that stops people is that Make.com only calls HTTPS and rejects self-signed certificates, so the solver needs a real address.

nodriver is fully async, so a blocking solve stalls the socket that drives your browser. Use the async client, read the sitekey with bracket access, and inject the token with evaluate.

Camoufox runs every script you pass to evaluate in an isolated scope, so the usual token injection changes nothing. Turn on main world eval, prefix the script, and the form submits.

An Actor runs in Apify’s cloud, so 127.0.0.1 is the container, not your desk. Run the solver in Server mode, store its address as a secret input, and switch hosts with isAtHome().

A Code by Zapier step gets 10 or 30 seconds by default and a solve takes longer. Submit in one step, delay, poll in the next, and run the solver in Server mode so Zapier can reach it.

DrissionPage drives real Chrome over CDP, so the token still has to go in by JavaScript. Read the sitekey, solve on 127.0.0.1, inject with run_js, and watch for the element that fails silently.

k6 has no npm and no Node modules, so the SDK is out. Two k6/http calls against the raw API, solved in the setup stage, with thresholds that still measure your app.

The solve belongs in the test process, not inside browser.execute. One custom command, one config change, and a spec that gets through a protected form.