Mobile Proxy for Make.com
Make.com (formerly Integromat) exposes proxy fields directly on the HTTP module. No code, no third-party relay — paste in the carrier IP host and you're done. This guide walks through scenario setup, rotation, and the small gotchas around Make's certificate handling.
Prerequisites
- →Make.com account with a Core or Pro plan (the proxy field is available on all paid tiers).
- →Mobile proxy slot at mobileproxies.org + an API key.
- →Permissions to install custom Data Stores (used for rotation counters).
Step-by-Step Configuration
Add a Data Store with proxy credentials
Make.com → Data stores → Add data store with structure:
Data store name: mobileproxies-creds Fields: host (text) port (number) user (text) pass (text) ← mark "do not store this in logs" apiKey (text) slotId (text) Insert one record: host=proxy.mobileproxies.org port=8000 user=u_4a9c pass=p_2X7q... apiKey=YOUR_API_KEY slotId=us-mob-01
Read credentials at the start of every scenario
First module in your scenario: Data stores → Get a record by keydefault. The output exposes host, port, user, pass as merge fields.
Configure HTTP → Make a request
Add the HTTP > Make a request module. Click Show advanced settingsand fill the proxy fields with merge tags from step 2:
URL: {{TARGET_URL}}
Method: GET
Headers: User-Agent → Mozilla/5.0 (iPhone)
— Advanced settings —
Use HTTP proxy: Yes
Proxy host: {{1.host}}
Proxy port: {{1.port}}
Proxy username: {{1.user}}
Proxy password: {{1.pass}}
Self-signed cert.: No (the carrier termination uses real CAs)
Timeout: 30
Follow redirects: Yes
Parse response: YesAdd a rotation step
Drop a second HTTP module before the scrape module that calls our switch endpoint. This one does not need to go through the proxy — it talks to our control plane:
URL: https://buy.mobileproxies.org/api/v1/proxies/{{1.slotId}}/switch
Method: POST
Headers: Authorization → Bearer {{1.apiKey}}
Body: (empty)
Use proxy: NoAdd a Tools → Sleep module after rotation (4 seconds) to let the new IP bind.
Pipe results downstream
The HTTP module's data output goes into a parser (Tools → Parse JSONfor APIs or Text parser → Match pattern for HTML), then into Sheets, Airtable, Postgres, or whatever destination you've already wired into Make.
Verify It Works
Run the scenario once with TARGET_URL set tohttps://api.ipify.org?format=json. The HTTP module's data bundle should contain a mobile IP. Compare theorg field on ipinfo.io against carrier ASNs. If Make.com's own datacenter IP comes back instead, the "Use HTTP proxy" toggle is off — most common mistake.
Smarter Rotation: Iterator Pattern
If your scenario iterates over a long array of URLs, you don't want to burn a rotation per URL. Use a Tools → Increment function and rotate only every N iterations:
Router branch A — when {{mod(counter; 25) = 0}}:
HTTP "rotate" → Sleep(4s) → HTTP "scrape"
Router branch B — else:
HTTP "scrape"
(The Increment function reads/writes the Data Store record so the counter
persists across scenario runs.)Common Errors
"unable to verify the first certificate"
Make.com's HTTP module pins certificate chains aggressively. Turn off Reject unauthorized on the advanced tab only if you trust the target — but mobile proxies don't require this for real CAs.
"connect ECONNREFUSED" to the proxy port
You're using the SOCKS5 port (8001) on Make's HTTP-only proxy field. Use the http_port (8000) — Make.com does not support SOCKS5.
Scenario stops at "Maximum number of operations exceeded"
Each HTTP call counts as one operation. If you rotate per URL, your operations doubles. Use the iterator pattern above to amortize.
Related Guides
Real Mobile IPs Inside Every Scenario
$5 trial. Plug the host into the HTTP module and your scenarios egress from carrier ASNs.