← Guides

Give your n8n workflows a static IP

APIs from banks, payment providers, ERPs and many B2B partners only accept requests from registered IP addresses. n8n Cloud and most container hosts send requests from shared or changing IPs. The fix takes two minutes.

Updated 2026-11-19 · 4 min read

Use the Proxy option of the HTTP Request node

Open the HTTP Request node, click Add option → Proxy, and paste your proxy URL. Only this node uses the static IP; the rest of your workflow is unchanged.

http://app:[email protected]:3128

Check that it works

Add a test HTTP Request node with the proxy option and call https://ifconfig.me. The response body should be your static IP.

Self-hosted n8n: proxy everything (optional)

If every outbound call must come from the static IP, set proxy environment variables on the n8n container and exclude internal hosts:

HTTP_PROXY=http://app:[email protected]:3128
HTTPS_PROXY=http://app:[email protected]:3128
NO_PROXY=localhost,127.0.0.1,postgres,redis

Tell your partner one address

Send them the single IPv4. Because the server is dedicated to you, the address never changes and nobody else uses it.

Tips

Skip the setup

A dedicated server and static IPv4 in 38 cities, ready in about 3 minutes. WireGuard for people, SOCKS5/HTTP proxy for code. From $9.99/month.

FAQ

Questions, answered.

Something else? Open a ticket, a human replies.

Does it work with Make or Zapier? +

Make and Zapier run on their own infrastructure without a per-request proxy option for most modules. A common pattern is a small relay (for example an n8n or serverless endpoint) that calls the partner API through your static IP.

Can I use SOCKS5 instead? +

The HTTP Request node proxy expects an HTTP proxy URL, so use port 3128. SOCKS5 on port 1080 is there for tools that need it.

More guides

Stop getting blocked. Start getting allowlisted.

Your own static IP, live in minutes. Full refund within 3 days if it is not right for you.