n8n
n8n is a workflow automation tool whose HTTP Request node accepts a proxy per request. Useful for low-code pipelines that scrape, monitor, or post to web services through helodata.
HTTP Request node
Drop an HTTP Request node.
Settings → Proxy (under the gear icon).
Fill in:
Residential / Mobile (gateway)
Proxy URL
http://helo_s1a2b3c4d5e-type-res-region-us:PASSWORD@gate.helodata.io:7777
ISP
Proxy URL
http://helo_s1a2b3c4d5e:PASSWORD@198.51.100.42:8000
Save → Execute Node to test.
[screenshot: n8n HTTP Request node with Proxy URL field]
Workflow-wide proxy via env vars
For the n8n process itself (so every HTTP node inherits), set environment variables before launch:
export HTTP_PROXY="http://helo_s1a2b3c4d5e-type-res-region-us:PASSWORD@gate.helodata.io:7777"
export HTTPS_PROXY="$HTTP_PROXY"
n8n startn8n's underlying axios/HTTP layer honors these.
Rotating IPs across runs
Use n8n's Function node to generate a fresh session per execution:
Pass {{ $json.proxy_url }} into the HTTP Request node's Proxy field.
ISP IP pool
Store your ISP list in a Set node (or fetch from a sheet/DB), pick a row via a Function node, and feed it into HTTP Request:
Verify
Point the HTTP Request at https://ipv4.icanhazip.com and inspect the response.
Common pitfalls
Self-hosted n8n behind a corporate proxy — n8n's HTTP node doesn't chain proxies. Only the last-set proxy wins.
Special characters in password — URL-encode (
@→%40).Webhook trigger nodes don't go through proxies — they receive inbound traffic. Only outbound HTTP Request nodes do.
Last updated
Was this helpful?