Skip to content
Get Started
G2G2
4.7/5
Excellent
Trustpilot

How to use a proxy in n8n

In n8n, open the HTTP Request node, click Add option → Proxy and enter http://USERNAME:PASSWORD@HOST:PORT. On self-hosted n8n you can instead set HTTPS_PROXY and HTTP_PROXY (plus NO_PROXY) so the HTTP traffic of every node goes through the proxy.

Try Now for $4.99Continue with Google
  • Session Control
  • High Speed
  • Privacy First

What you need

n8n workflows call APIs and fetch pages from wherever n8n runs, usually a cloud server whose IP is shared, flagged or outside the US. A CleanProxies IP gives those requests a fixed US address you can add to an API's allowlist, or a residential IP per request for scraping steps.

Your credential line

From the dashboard's proxy manager: host (or IP), port, username and password. Convert lists with the proxy list formatter.

n8n ready

  • n8n Cloud or self-hosted n8n with the HTTP Request node.
  • For instance-wide routing: access to the environment of your self-hosted n8n (Docker, npm or Kubernetes).

Which proxy fits n8n?

Both products use the same setup in n8n. What changes is how long an IP stays with you.

Static ISP Proxies

Best fit

Put one 100% dedicated US ISP IP in the nodes that call allowlisted APIs or logged-in accounts. It stays the same on every execution, all month, with unlimited bandwidth for busy workflows.

starting from$0.75/IP

Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.

Buy NowSee Static ISP Proxies features

Rotating Residential Proxies

Also works

A rotating line can give each request a new residential IP from 50M+ IPs in 190+ countries, which suits scraping steps. When a workflow logs in and then fetches several pages, use a sticky line (5 minutes to 24 hours) so the steps share one IP.

starting from$0.63/GB

Residential IPs in 190+ countries with country, state and city targeting. Rotate on every request or hold a sticky session for up to 90 minutes; GB never expire.

Buy NowSee Rotating Residential Proxies features
credentials

Your CleanProxies credentials

Every product connects over HTTP(S); static ISP and ISP subnet proxies also run SOCKS5 and IP whitelisting. This is what the dashboard gives you to paste into n8n.

Static ISP and ISP subnetHTTP(S)SOCKS5IP whitelist
IP:PORT:USER:PASS

One line per dedicated IP. With IP whitelisting on, the line is just IP:PORT and no password is sent.

Rotating residential and mobileHTTP(S)User:pass
HOST:PORT:USER:PASS

Generated in the proxy manager. The username carries the location and session you pick, so generate a new list to change them.

As a URL, for code and most toolshttp://USERNAME:PASSWORD@HOST:PORTsocks5://USERNAME:PASSWORD@HOST:PORT

Use http:// even for HTTPS websites; the TLS session still runs end to end. The socks5:// form is for static ISP and ISP subnet proxies.

How to set up CleanProxies in n8n

Four steps, then check the exit IP with the free proxy checker.

  1. 1

    Add an HTTP Request node

    Set Method and URL as usual. For a first test, use GET and https://api.ipify.org?format=json.

  2. 2

    Add the Proxy option

    At the bottom of the node, click Add option and choose Proxy. It applies to this node only and overrides any proxy environment variables.

  3. 3

    Enter the proxy URL

    Type http://USERNAME:PASSWORD@HOST:PORT from your dashboard line. Keep the http:// scheme: n8n only uses http:// and https:// proxy URLs.

  4. 4

    Execute the step

    Click Execute step. The output's ip field should be the CleanProxies IP, not your n8n server's address.

settings

n8n proxy settings

Replace the highlighted placeholders with the values from your dashboard. Pick an example to see its code.

n8n + CleanProxies

What the Proxy option accepts

The field takes one proxy URL. Credentials in the URL are sent to the proxy as Proxy-Authorization, and HTTPS targets are tunnelled with CONNECT, so the TLS session stays end to end.

Proxy option valueText
http://USERNAME:PASSWORD@HOST:PORT
  • A socks5:// value isn't used: n8n logs a warning and falls back to the environment settings. Keep the ISP list on HTTP(S) in the dashboard for n8n. URL-encode special characters in the password (@ becomes %40).

Patterns that work well

  • One ISP IP per workflow that talks to an IP-allowlisted API or a logged-in account, so the address never changes between executions.
  • Proxy per item: the Proxy field accepts expressions, so {{ $json.proxy }} can pick a different line for each incoming item.
  • On a rotating residential line, use the node's Batching option (Items per Batch, Batch Interval) to pace requests instead of firing hundreds at once.
fix it fast

Troubleshooting n8n proxy errors

Verify your exit IP

Paste the node below onto the canvas (it is plain n8n workflow JSON), open it and click Execute step. The ip in the output should match your CleanProxies line.

Open What is my IP? through the proxy to see the address and headers a website receives, or paste up to ten lines into the free proxy checker to test connectivity, latency and exit IP.

Still stuck? Our 24/7 support team answers fast: contact us with the error and the line you used (leave the password out).

n8n error fixes
  • Requests still leave from the server's IPWhy: The Proxy value starts with socks5:// or isn't a valid URL, so n8n ignores it and falls back to the environment.Use http://USERNAME:PASSWORD@HOST:PORT exactly, with the scheme.
  • 407 Proxy Authentication RequiredWhy: Wrong credentials, or a special character in the password breaking the URL.Copy the line again from the dashboard and URL-encode the password.
  • Calls to internal services fail after setting HTTP_PROXYWhy: Internal hostnames are being sent to the proxy, which can't reach your private network.List those hosts in NO_PROXY (comma-separated) and restart n8n.
  • Environment variables seem to have no effectWhy: The container wasn't recreated, or lowercase variables set elsewhere take precedence.Recreate the container (docker compose up -d) and check for http_proxy/https_proxy in the environment.
  • Timeouts on slow targetsWhy: The node's Timeout option is shorter than the target needs through a residential IP.Raise Timeout under Add option and pace large runs with Batching.

n8n proxy guides

Setup guides and best practices from the CleanProxies blog.

Get the latest insightsAll Blogs

More integrations

Setup guides for tools people run next to n8n.

All integrations

n8n proxy FAQs

Straight answers about running CleanProxies in n8n.

Yes. Put the username and password in the proxy URL, for example http://USERNAME:PASSWORD@HOST:PORT, and URL-encode any special characters in the password.

Got more questions?All FAQs