Skip to content

Use a mobile proxy in an n8n HTTP Request node

Configure the HTTP Request node's Proxy option, keep proxy authentication separate from destination authentication and test the connection before scheduling a workflow.

Mobileproxies.orgUpdated 4 min read

Set the HTTP Request node's Proxy option to the issued proxy URL. Proxy authentication belongs to that connection; the node's destination credentials authenticate to the target service and do not automatically configure the proxy.

Collect the connection details

From your active rental, obtain the HTTP proxy host, port, username and password. Confirm the rental is still active and that the client can reach the endpoint. The HTTP Request node's proxy setting is for HTTP proxy configuration; do not assume a SOCKS5 URL works in the same field.

Build a proxy URL with correctly URL-encoded credentials. Avoid placing the raw URL in an exported workflow. On a controlled self-hosted instance, environment variables may be an option if your deployment allows nodes to access them. On a hosted or restricted instance, use the secret-management options supported by that deployment.

Configure a small manual test

  1. Create a Manual Trigger and an HTTP Request node.
  2. Choose GET and use an IP-echo endpoint, such as https://api.ipify.org?format=json.
  3. In the node options, add Proxy and supply the authenticated HTTP proxy URL through your approved secret configuration.
  4. Set a request timeout and enable the response status code in the output.
  5. Execute once. Compare the returned IP with a direct request, then test a small authorized destination request.
n8n expressions
// HTTP Request > Options > Proxy
// Self-hosted example only, when environment access is permitted:
{{ $env.MP_PROXY_URL }}

// HTTP Request > URL
https://api.ipify.org?format=json

Do not disable your instance's environment-access restrictions just to copy this example. Check the n8n version and deployment settings, then use a supported credential or secret-management method.

Keep proxy and destination credentials separate

A destination API key belongs in the authentication mechanism that API specifies. It is not a replacement for the proxy username and password. Likewise, adding a custom X-Proxy header to a destination request does not make n8n route that request through a proxy.

Only the nodes configured to use the proxy will follow that route. Verify each HTTP node used by the workflow. Test the same host and method your task will use, since a successful IP lookup does not prove that a destination will allow the request.

Add scheduling after the manual test works

Use a bounded schedule, timeouts and explicit error handling. Start with a low request rate and check execution retention so that response bodies or credentials are not saved unnecessarily.

For rotation, use the interface provided by your rental. Pause work during a reconnect and verify the new connection before continuing. This guide does not prescribe an undocumented API route.

Download the manual health-check workflow

Sources and further reading