n8n proxy setup
Workflow automation with an HTTP Request node. Point it at the Eveses residential pool with the configuration below — the geo lives in the username, so nothing else in your setup has to change to move country.
proxy.eveses.com:12321 · SOCKS5 on 32325 · 199 countries · from $7.35/GB
The HTTP Request node has a Proxy field under Options, but it takes ONE url string with the credentials inline — there is no separate auth field, and the node will not read `HTTP_PROXY` from the container.
Configuration
HTTP Request node → Options → Add option → Proxy
http://eveses_user_country-us:[email protected]:12321
For a self-hosted instance, the same value as an environment variable
applies to every node at once:
HTTP_PROXY=http://eveses_user_country-us:[email protected]:12321
HTTPS_PROXY=$HTTP_PROXYNotes for n8n
Put the credential in an n8n credential rather than the node body if the workflow is shared.
Change the geo per run by templating the username from a workflow variable.
Change country without touching n8n
eveses_user_country-deeveses_user_country-de_session-ab12cd34_lifetime-30mThe geo and the session live in the username, not in the host or the port. Every configuration on this page stays exactly as it is when you move country — you edit one string. 199 countries are addressable, with city and state tokens inside most of them.
FAQ
How do I set a proxy in n8n?›
How do I choose the country n8n exits from?›
How do I keep the same IP across requests in n8n?›
What does this cost?›
Other integrations
Run n8n through residential IPs
$7.35/GB at 1 GB, $2.57/GB in volume — same credentials in every tool.
Get proxies →