Open-source workflow automation platform. Route n8n HTTP requests through KnoxProxy for web scraping, data collection, and API monitoring workflows.
Navigate to your workflow editor.
Drag an HTTP Request node into your workflow.
In node settings, enable "Proxy" and set details.
Proxy URL: http://USER:PASS@gw.knoxproxy.com:7000Enter the target URL in the HTTP Request node.
Modify proxy username.
Proxy URL: http://USER-country-us:PASS@gw.knoxproxy.com:7000Execute the node and check the output.
{
"node": "HTTP Request",
"parameters": {
"url": "https://httpbin.org/ip",
"options": {
"proxy": "http://USER:PASS@gw.knoxproxy.com:7000"
}
}
}Each HTTP Request execution gets a new IP. For workflows that need the same IP across nodes, use -session-{workflowRunId}.
| Problem | Fix |
|---|---|
| Request failed with status 407 | Verify credentials in proxy URL. |
| Connection timeout | Increase timeout in node settings. |
USER-country-de-city-berlin-session-profile07Order matters -- geo flags before the session flag. The session name is free text; use the profile ID so the mapping is self-documenting. Password stays as issued; no flags belong there. HTTP on :7000, SOCKS5 on :7001, same credentials.
Yes. n8n cloud supports the same HTTP Request node proxy field as a self-hosted instance, so enter your KnoxProxy URL there in the format http://USER:PASS@gw.knoxproxy.com:7000. The workflow then routes that request through KnoxProxy from n8n cloud servers, with no extra setup needed beyond the proxy field itself.
Each workflow execution triggers a new HTTP Request, and every request gets a fresh KnoxProxy IP by default with no extra configuration needed. If a workflow instead needs the same IP across multiple runs, append -session-{workflowRunId} to the proxy username so every node call in that run shares one sticky exit IP.
Yes. Add an HTTP Request node configured with your KnoxProxy proxy URL to fetch pages, then chain it into HTML Extract and Set nodes to parse and structure the scraped data. This low-code combination builds a full scraping workflow without writing any code, and country targeting works the same way as any other integration.
The built-in HTTP Request node only supports HTTP proxies, so it works directly with the KnoxProxy gateway at gw.knoxproxy.com:7000. For SOCKS5, add a Code node and use a JavaScript library such as socks-proxy-agent, pointing it at the KnoxProxy SOCKS5 port 7001 to handle the connection manually inside the workflow.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.