Add a Mobile Proxy to n8n (HTTP Request Node)

n8n's HTTP Request node can send its requests through a proxy, and it takes one field to set up. Here's exactly where that field is, what to paste into it for a RelayKit mobile proxy, how to prove it's working, and a small scheduled workflow that checks a price from a real US mobile IP.

1. The value you'll paste

n8n's Proxy option takes an HTTP proxy URL with the username and password in it:

HOST, USER and PASS are on your proxy card in the RelayKit dashboard (My Proxies). The HTTP port on Multi Location and Single Location proxies is 8000. The quickest way to get the exact string: open the card, click 🤖 Use with AI tools, choose n8n HTTP Request, and copy. The panel also lists these steps.

2. Set it in the HTTP Request node

1. Add an HTTP Request node to your workflow.
2. Set Method to GET and URL to https://api.ipify.org?format=json for the first test.
3. Scroll to Options → Add Option → Proxy.
4. Paste http://USER:PASS@HOST:8000 into the Proxy field.
5. Click Execute step.

The Proxy option applies to that node only, and it overrides any HTTP_PROXY environment variable set on the n8n server. Other nodes in the workflow keep using n8n's normal connection unless you set the option on them too.

3. Verify

The test node's output should contain an ip that matches the IP on your proxy card. If it shows your server's own IP, the option didn't apply; re-open Options and confirm the Proxy value is set. A 407 error means the username or password is wrong, or that IP Whitelisting is on for the proxy; in whitelist mode the proxy expects no password and only accepts the whitelisted IP, so either whitelist your n8n server's public IP and use http://HOST:8000, or turn whitelisting off.

4. Workflow: daily price check from a US city

A typical use for a mobile proxy in n8n is seeing a page the way a visitor in a specific US city sees it, on a schedule. With a RelayKit Multi Location proxy you choose that city in the dashboard and can change it any time.

1. Schedule Trigger — every day at a fixed time.
2. HTTP Request — GET the page you're monitoring, with the Proxy option set as above. Under Options, set Response → Response Format to Text if the page is HTML.
3. HTML node — Extract HTML Content, with a CSS selector for the price element (for example .price). Return an array if there are several.
4. Set node — add date ({{ $now.toISODate() }}) and city (the city your proxy is in) alongside the extracted price.
5. Google Sheets / Airtable / Postgres node — append the row.
6. Optional: an IF node that compares today's price with the last stored value and sends a Slack or email alert when it changes.

To compare several cities, duplicate the HTTP Request → HTML → Set branch once per proxy, each with its own Proxy value, or keep one branch and switch your Multi Location proxy's city in the dashboard between scheduled runs.

5. Notes and limits

• HTTP proxy only. The n8n Proxy option is described as an HTTP proxy setting and doesn't take socks5:// URLs. Use port 8000, not 9000.
• One node at a time. There is no workflow-wide proxy switch in the node; set the option on each HTTP Request node that should use the proxy.
• Credentials in the field. The value includes your proxy password. Treat exported workflow JSON accordingly, or use IP whitelisting so the value holds no password.
• Unlimited data. RelayKit Multi Location and Single Location proxies aren't metered per GB, so a scheduled workflow doesn't eat into a quota.
• Fresh IP. Click Reset IP on the proxy card, or set a rotation timer there. The Proxy value in n8n stays the same.

Related guides