Direct Answer
Make.com (formerly Integromat) now supports proxies natively. In the new HTTP app (v4, released December 2025), open Advanced Settings and create a Proxy keychain with your German mobile proxy host, port, username, and password. Every request from that HTTP module then exits through the German mobile IP — no external relay needed. Only the older legacy HTTP module lacks a proxy field.
Set the Proxy in Make's New HTTP App (the direct way)
Make's HTTP app was overhauled on 2 December 2025 with native, no-code support for proxies (alongside mTLS and a secure keychain). That means you can point a scenario at your own German mobile endpoint straight from the module — the limitation that older "Make proxy" guides describe is gone.
To route an HTTP module through your German mobile proxy:
- Add an HTTP module to your scenario and choose the new HTTP app (the current version, not the legacy "HTTP" module).
- Open Advanced Settings on the module.
- Next to Proxy, click Create a keychain.
- Fill in the proxy fields from your dashboard:
- Host — the proxy host (domain or IP).
- Port — the proxy port (1–65535).
- Username — your proxy login.
- Password — your proxy password.
- Save the keychain and run the module. That request now leaves through your German mobile IP.
The credentials live in Make's keychain, separate from the request, so you can reuse the same proxy across modules and scenarios without re-typing it.
Make HTTP module (v4) ──▶ Advanced Settings ▸ Proxy keychain ──▶ German mobile IP ──▶ target site
The Alternative — A Proxy Relay You Control
If you're still on the legacy HTTP module (no proxy field), or you want the proxy to live on infrastructure you fully control, use a relay instead of the in-app keychain:
- Stand up a small relay that holds the proxy. A self-hosted n8n instance is the simplest — it can route its HTTP Request node through your German mobile proxy. See how to use a German mobile proxy with n8n.
- Expose one webhook on the relay that takes a target URL (and any params) and returns the fetched data.
- Call the relay from Make. In your scenario, use the HTTP module to POST the target URL to your relay's webhook. The relay makes the actual request through the German mobile IP and hands the result back to Make.
Make orchestrates; the relay does the proxied request. This pattern also gives you a single place to manage rotation, retries, and logging outside of Make.
Make scenario ──HTTP POST {url}──▶ your relay (n8n + German mobile proxy) ──▶ target site
◀──── JSON result ─────
Alternative: Run the Request Step in Code You Host
If you already run a small serverless function or worker, the same idea applies: Make calls your function, the function uses the proxy (HTTP client with proxy= / proxies=), and returns the data. The proxy lives where you control the outbound request.
Verify the German IP
Whichever route you use, verify the exit before you trust it. Add an HTTP request to an IP-echo endpoint (e.g. https://api.ipify.org) and confirm it returns your German mobile IP — for the in-app keychain, run the module directly; for a relay, test the relay on its own first. Once the exit is correct, the rest of the scenario simply receives German-sourced data.
Automate Responsibly
A mobile proxy improves reliability for legitimate automation — it is not a tool to circumvent access controls or platform rules. Respect each target's robots.txt and terms, keep request rates reasonable, collect only what you need, and handle any personal data in line with the GDPR. For the legal side, see is web scraping legal? EU & GDPR.
FAQ
Can I set a proxy directly in Make's HTTP module?
Yes. The new HTTP app (v4, released December 2025) has a native Proxy field under Advanced Settings. Create a Proxy keychain with your host, port, username, and password, and that HTTP module routes through it. Only the older legacy HTTP module lacks a proxy field.
What's the simplest way to add a German mobile IP to Make?
Use the new HTTP app: add a Proxy keychain in Advanced Settings with your German mobile proxy credentials. If you're on the legacy HTTP module or want central control, route through a relay you control — a self-hosted n8n instance with the proxy configured — and have Make call its webhook.
Does changing my Make organisation zone give a German IP?
No. Zone selection changes Make's data region, not a controllable exit IP, and it can't be relied on as a German mobile vantage point. Use the HTTP app's Proxy keychain instead.
Is this the same for Zapier?
Not quite — Zapier still lacks a native proxy field, but it does allow a Python code step you can route through a proxy. See how to use a German mobile proxy with Zapier.
CTA
Give your automations a real German mobile IP — set it in Make's HTTP keychain or on your own relay. Start with a German mobile proxy — HTTP/SOCKS5/OpenVPN, sticky sessions, fair-use 20 GB/day.
Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — browse German mobile proxy plans or try a shared 5G German proxy.