n8n Proxy Setup: Route Workflows Through a German Mobile IP

Direct Answer

n8n routes through a German mobile proxy in two ways: per request via the HTTP Request node's Proxy option (http://USER:PASS@HOST:PORT), or instance-wide on a self-hosted n8n by setting the HTTP_PROXY and HTTPS_PROXY environment variables. n8n uses Axios internally, so it reads these standard proxy variables for all node traffic.

What to Know Before You Start

n8n is a workflow-automation tool you can self-host — which is exactly why it pairs well with your own proxy (and fits a privacy-conscious, EU-based stack). Two honest points:

Self-hosting gives you the env-var route. Setting HTTP_PROXY/HTTPS_PROXY requires control of the instance, so it applies to self-hosted n8n, not the managed cloud.
HTTP proxy is the reliable path. n8n's outbound calls go through Axios, which honours HTTP(S) proxy variables. SOCKS via env var is unreliable here, so use an HTTP endpoint.

You'll need from your GermanProxy.io account: host, port, username and password.

Method A — Per Request (HTTP Request node)

Add or open an HTTP Request node.
Open the node's options/settings and find the Proxy field.
Enter your endpoint as http://USER:PASS@PROXY_HOST:PORT.
Execute the node — that request now exits through your German mobile IP.

Use this when only specific calls in a workflow should be proxied. The node's Proxy field also takes precedence over the instance-wide environment variables below, so you can override a global proxy per request.

Method B — Instance-wide (self-hosted env vars)

Set the proxy variables for your n8n process/container:

HTTP_PROXY=http://USER:PASS@PROXY_HOST:PORT
HTTPS_PROXY=http://USER:PASS@PROXY_HOST:PORT
# Optional fallback for both schemes:
ALL_PROXY=http://USER:PASS@PROXY_HOST:PORT

For Docker, pass them with -e HTTP_PROXY=... (or in your compose environment: block) and restart. n8n then routes standard node HTTP traffic through your German mobile IP. One caveat: a few nodes that bundle their own HTTP client — notably the AI/LangChain nodes (OpenAI, Gemini) — ignore these env vars and still call out directly, so always verify with an IP check (below). Also note that a lowercase http_proxy takes precedence over the uppercase HTTP_PROXY if both are set.

Verify the IP First

Add an HTTP Request node pointing at an IP-echo endpoint (e.g. https://api.ipify.org) and execute it. The output should be a German mobile IP. If it's your own address, re-check the proxy field / env vars. A 407 means auth didn't reach the proxy — see how to fix 407 proxy authentication required.

Sticky Sessions vs. Rotation

A single dedicated German endpoint keeps a stable IP across a workflow run; rotate on demand at the proxy to spread load. The country stays German throughout. See sticky sessions and IP rotation explained.

Automate Responsibly

A mobile proxy improves reliability for legitimate automation and data collection — it is not a tool to circumvent access controls or platform rules. Respect each target's robots.txt and terms, keep request rates reasonable, collect only what you need, and handle any personal data in line with the GDPR. For the legal side, see is web scraping legal? EU & GDPR.

FAQ

Does the HTTP Request node have a proxy field?

Yes. Set your endpoint in the node's Proxy option to route just that request. For all nodes at once, use the environment variables on a self-hosted instance.

Can I use this on n8n Cloud?

The HTTP Request node's per-request proxy field works regardless. The HTTP_PROXY/HTTPS_PROXY env-var route needs a self-hosted instance you control.

Why doesn't my SOCKS5 proxy work via env var?

n8n's Axios-based HTTP layer reads HTTP(S) proxy variables; SOCKS through env vars is unreliable. Use an HTTP endpoint. See SOCKS5 vs HTTP proxy.

Where do I store the credentials safely?

Use environment variables (optionally n8n's _FILE file-based config) rather than hard-coding them in a node.

CTA

Run your n8n workflows on real German mobile IPs. Start with a German mobile proxy — HTTP/SOCKS5/OpenVPN, sticky sessions, fair-use 20 GB/day.

Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — compare German mobile proxy plans or start small with a shared 5G proxy.