TL;DR
Make runs your HTTP requests from shared cloud IPs that thousands of other scenarios also use. If a target site blacklists one of those IPs, every scenario routing through it gets blocked too, including yours. Proxyon gives your HTTP module a dedicated IP so your automation stands on its own. Add your credentials under the module's Proxy field in Advanced Settings, match the proxy type to your workflow, and your scenario stops sharing risk with strangers.
Why Make Requests Get Blocked
Make's HTTP module sends requests from a small pool of IPs shared across the entire platform. That works fine for APIs with generous rate limits. It falls apart the moment your target tracks IP reputation, since you have no control over who else is hitting that same address.
One scenario scraping too aggressively, or hitting a site that bans on sight, can get an IP flagged. Every other Make user on that IP inherits the block, yours included, even if your requests were clean. There's no way to see it coming and no way to fix it from your end.
A dedicated proxy solves this by putting your scenario on its own IP. Nobody else's traffic touches it, so nobody else's mistakes become your problem. This matters most for scraping, price monitoring, and any workflow hitting a target more than once.
Also Read: What is a Web Scraping Proxy and Why You Need One
How to Add a Proxy to Make's HTTP Module
- Grab your credentials from your Proxyon dashboard: host, port, username, password.
- In your Make scenario, open the HTTP app and add a Make a Request module.
- Fill in your URL, method, and authentication as usual, then scroll down to Advanced Settings.
- Find the Proxy field and click Create a Keychain.
- In the popup, enter your Proxyon host and port, then your username and password if the proxy requires authentication.
- Save the keychain and run the module once to confirm the connection returns data instead of an error.
- Reuse the same keychain across modules that should share an IP, or create a new one per scenario if you need separation.
If the module errors out immediately, check the credentials against your Proxyon dashboard first. An inactive plan or a typo in the host field is the usual cause.
What Proxy Type Should You Use in Make
Don't pick a proxy type in the abstract. Pick it based on what the module is actually doing on the other end of the request.
Scraping product pages, social profiles, or ad placements: use residential proxies. These targets fingerprint traffic and block datacenter ranges on sight, so a household IP is the only way through consistently.
Pulling from a public API or a site with no real bot protection: use datacenter proxies. You're paying for speed and volume here, not stealth, so there's no reason to pay residential prices.
A scenario that runs on a schedule (hourly, daily, on a trigger) against the same target for weeks: keep the same dedicated IP across every run instead of rotating. Platforms track behavior over time on a single IP, and a consistent address builds trust the way a fresh one never does. Rotating proxies actually work against you here, since each run looks like a new, unknown visitor.
A one-off scenario that fires once and never touches that target again: rotation doesn't matter and a cheaper datacenter IP is fine, since there's no history to protect.
The failure mode to avoid: using the same proxy type for every module in a scenario because it's easier to set up once. A scenario that scrapes a protected site and then posts the result to an API doesn't need residential for both steps, only for the step that needs it.
FAQ Section
Can I share one Proxyon proxy across multiple Make scenarios?
You can, but only if those scenarios hit different targets or don't need IP separation. If two scenarios scrape the same site, share the proxy and you're back to the shared-risk problem you were trying to avoid.
Does the proxy setting work on every HTTP module?
It's available on Make a Request and other HTTP app modules under Advanced Settings. Non-HTTP app modules (native integrations like Slack or Google Sheets) don't route through a custom proxy.
What if my scenario still gets blocked after adding a proxy?
Check whether the target is blocking on something other than IP, like request headers or rate. A dedicated IP fixes IP-based blocks, not every kind of block.
Do I need a paid Proxyon plan to test this?
No. New accounts get free residential bandwidth to verify the connection before funding an account.
Final Thoughts
Make gives you the automation engine. Proxyon gives it an IP that isn't shared with strangers. Residential and datacenter proxies both start from $1.75/GB and $1.50/IP, pay-as-you-go with no subscription. Deposit $5 and plug it into your next scenario.
