Make.com Proxy Configuration

Make.com (formerly Integromat) is a visual automation platform that connects apps and services through scenarios. When scenarios include HTTP modules that access external websites, proxy infrastructure ensures requests are not blocked by anti-bot protections.

Why Make.com Scenarios Need Proxies

Make.com scenarios that access external websites face blocking because:

• **Shared infrastructure IPs**: Make.com executes scenarios on shared cloud infrastructure. Target websites may have already flagged these IP ranges due to other users' activities.
• **Automated access patterns**: Scenarios running on schedules create predictable request patterns that anti-bot systems detect.
• **Rate limiting**: External APIs and websites rate-limit requests from known automation platform IP ranges.
• **Geo-restriction**: Some content is only accessible from specific geographic locations.

Configuring Proxy in Make.com HTTP Module

Make.com's HTTP module supports proxy configuration:

1. Add an **HTTP > Make a request** module to your scenario.
2. Expand the **Advanced settings** section.
3. Set **Use proxy**: Yes
4. Enter proxy details:
5. - **Proxy URL**: `http://gate.hexproxies.com:8080`
6. - **Proxy Username**: `user` (or `user-country-us` for geo-targeting)
7. - **Proxy Password**: your Hex Proxies password

Module: HTTP > Make a request
URL: https://target-site.com/data
Method: GET
Advanced Settings:
  Use Proxy: Yes
  Proxy: http://user:pass@gate.hexproxies.com:8080

Common Make.com Proxy Scenarios

#### Price Monitoring Scenario

Scheduler → HTTP Request (proxied) → JSON Parse → Filter (price changed) → Google Sheets → Email

The HTTP Request module uses Hex Proxies to reliably access pricing pages that block Make.com's default IPs.

#### Competitor Content Monitoring

Scheduler → HTTP Request (proxied) → Text Parser → Compare with Data Store → Slack Notification

Monitor competitor websites for content changes using residential proxies that maintain long-term access.

#### Multi-Region Data Collection

Scheduler → Iterator (countries) → HTTP Request (geo-proxied) → Aggregator → Google Sheets

Use different geo-targeted proxy credentials for each iteration to collect region-specific data:

In the Iterator module, output country codes. In the HTTP module, dynamically set the proxy username:

Proxy: http://user-country-{{1.country}}:pass@gate.hexproxies.com:8080

Make.com Webhook Scenarios with Proxy

For scenarios triggered by webhooks that then need to fetch external data:

Webhook → HTTP Request (proxied) → Process Data → Response

The proxy ensures the outbound HTTP request in the middle of the scenario accesses the target site reliably, regardless of Make.com's cloud IP reputation.

Limitations and Workarounds

Make.com's HTTP module has basic proxy support. For advanced proxy features:

• **Rotation**: Hex Proxies handles rotation at the gateway level. Each request through the gateway gets a different IP automatically.
• **Sticky sessions**: Append session IDs to the proxy username for multi-request flows within a scenario.
• **Authentication**: HTTP basic auth in the proxy URL works with Make.com's proxy field.

Cost Considerations

Make.com scenarios typically make targeted, low-volume requests. A scenario checking 20 URLs daily with 200 KB average response size uses approximately 120 MB per month. At residential rates, this costs about $0.51/month -- negligible proxy costs for reliable automation.