Visual workflow automation platform formerly known as Integromat. Route Make HTTP module requests through KnoxProxy to scrape websites, monitor APIs, and automate data collection workflows with residential and datacenter proxies.
Log in to Make and click "Create a new scenario" from the dashboard.
Click the "+" icon and search for "HTTP". Select "Make a request" from the HTTP module.
Enter your target URL in the URL field and select the appropriate HTTP method (GET, POST, etc.).
Scroll down to "Show advanced settings" and toggle it on. Find the "Proxy" field and enter your KnoxProxy details.
http://USER:PASS@gw.knoxproxy.com:7000To route through a specific country, modify the proxy username with a country suffix.
http://USER-country-us:PASS@gw.knoxproxy.com:7000Click "Run once" to test the module. Verify the response shows a proxied IP, then activate the scenario schedule.
{
"module": "http:ActionSendData",
"version": 1,
"parameters": {},
"mapper": {
"url": "https://httpbin.org/ip",
"method": "GET",
"headers": [],
"qs": [],
"bodyType": "",
"parseResponse": true,
"timeout": 30,
"shareCookies": false,
"followRedirect": true,
"followAllRedirects": false,
"rejectUnauthorized": true,
"proxy": "http://USER:PASS@gw.knoxproxy.com:7000"
}
}Each HTTP module execution receives a fresh IP by default. For sticky sessions across multiple modules in one scenario run, use USER-session-{scenarioRunId} as the proxy username.
| Problem | Fix |
|---|---|
| ConnectionError: 407 Proxy Authentication Required | Double-check username and password in the Proxy field. Ensure no trailing spaces. |
| RuntimeError: Operation timed out | Increase the Timeout value in advanced settings to 60 seconds or higher. |
| ScenarioError: ECONNREFUSED | Verify proxy is set to gw.knoxproxy.com:7000 for HTTP. Use port 7001 for SOCKS5. |
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. Make's cloud platform has no self-hosted option, so you enter the KnoxProxy proxy URL directly in the HTTP module's advanced settings, under the Proxy field. Make cloud then connects outbound to gw.knoxproxy.com on port 7000 for every scenario run, no local server or agent needed.
Each scenario execution automatically gets a new residential IP from KnoxProxy by default, since rotation happens server-side at the gateway with no configuration needed. If you instead want the same IP across an entire scenario run, add a USER-session-{scenarioRunId} suffix to the proxy username in the HTTP module.
Yes. Set a different proxy URL with its own country code on each HTTP module within a scenario, for example USER-country-de for Germany or USER-country-us for the US, entered under Show advanced settings. Each module then independently pulls data through a residential IP from its own targeted country.
The built-in HTTP module only supports HTTP and HTTPS proxies through its Proxy field, pointed at gw.knoxproxy.com on port 7000. For SOCKS5, which KnoxProxy exposes on port 7001, you need a Code module with a custom script, since the HTTP module has no SOCKS5 option.
Rotating residential proxies -- 3 minutes setup, instant activation, 14-day money-back guarantee.