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 proxy configuration in HTTP Request nodes. Enter the KnoxProxy URL in the proxy field.
Each execution gets a fresh IP by default. No extra configuration needed.
Yes. Use HTTP Request nodes with KnoxProxy for web scraping workflows. Combine with HTML Extract and Set nodes for data parsing.
n8n HTTP Request nodes support HTTP proxies. For SOCKS5, use a Code node with a library that supports SOCKS5 connections.
Free trial on rotating residential -- 3 minutes setup, no credit card.