Cloudflare Solver

action_cloudflare_solver · action · Utility · Available · v1.0.0

Description

Risolve Cloudflare/DDoS-Guard JavaScript challenge via FlareSolverr (https://github.com/FlareSolverr/FlareSolverr). Ritorna il cookie `cf_clearance` + User-Agent da usare nei fetch successivi al sito Cloudflare-protected. Setup: il tenant self-hosta FlareSolverr (1 docker container leggero) e configura qui l'endpoint. Bring Your Own — Zeli non gestisce solver pubblici per evitare abusi. USA SOLO per: accesso a PROPRI siti protetti da CF, monitoraggio uptime, integrazione partner B2B. NON usare per: evasione paywall/protezione siti di terzi (TOS violation, potenziale liability legale del tenant). Workflow tipico: 1) cloudflare_solver(url) → cookies+UA, 2) web_fetch_advanced(url, cookies=output.cookieHeader, UA=output.userAgent) → HTML reale. Use case: (1) monitoraggio uptime di propria pagina dietro CF, (2) audit periodico content proprio sito Cloudflare-protected, (3) integrazione partner B2B che usa CF managed challenge, (4) scraping pricing pages proprie multi-region.

⚙️ Configuration parameters

Fields shown in the editor when configuring the node. Generated directly from the NodeDefconfigFields.

Field	Type	Required	Default	Description
`url` URL Cloudflare-protected	`string`	yes	— https://miosito.com	URL del sito protetto da Cloudflare. Il solver fa GET e risolve il challenge JS.
`endpoint` FlareSolverr endpoint	`string`	no	— http://flaresolverr.local:8191 (vuoto = env FLOWFORGE_FLARESOLVERR_ENDPOINT)	URL del tuo FlareSolverr. Default container Docker: http://localhost:8191. Self-host: docker run -d -p 8191:8191 ghcr.io/flaresolverr/flaresolverr:latest
`cmd` Comando	`enum` `request.getrequest.postsessions.createsessions.destroy`	no	`request.get`	request.get = solve + GET URL. request.post = solve + POST. sessions.* = gestione persistent session (riduce solve time su request successive).
`sessionId` Session ID (opzionale)	`string`	no	— my-tenant-session-1	Riusa una session FlareSolverr esistente. Crea prima con cmd=sessions.create, poi riusa l'ID per skipare il solve ad ogni request. Auto-expire dopo idle.
`maxTimeoutMs` Timeout solve (ms)	`number`	no	`60000`	Tempo max che FlareSolverr ha per risolvere. Default 60s. Min 10s, max 180s.

⬆️ Node output

Fields available to downstream nodes via $node.<alias>.json.<field>:

cookies
cookieHeader
cfClearance
userAgent
html
finalUrl
sessionId

💡 Configuration example

JSON snippet of the node as it appears in the workflow. Values are derived fromdefaultValue and from required parameters.

{
  "id": "node-action_cloudflare_solver-1",
  "defId": "action_cloudflare_solver",
  "label": "Cloudflare Solver",
  "config": {
    "url": "https://miosito.com",
    "cmd": "request.get",
    "maxTimeoutMs": 60000
  }
}

🔗 Related nodes in the same category

Ready to use Cloudflare Solver?

Available now on all FlowForge plans. Try it free without a credit card.

Start free Browse all nodes