Mobile proxies for automation and bots
An automation running on a server goes out from a datacenter IP, the kind of address sites filter first. With a dedicated mobile proxy your scripts and workflows go out from a real carrier's 5G IP, in the country you choose, and you control them from code with our API.
- Real carrier mobile IPs, in the country you choose
- API to change IP, read status and set rotation
- Works with scripts, automated browsers and no-code tools
Always included
- 5G up to 100 Mbps
- Unlimited traffic
- Dedicated IP
- IP rotation: link or timer
- HTTP, SOCKS5 and VLESS
- VPN: WireGuard, OpenVPN
- Consistent TCP/IP fingerprint
- Instant activation
- No lock-in
- Dedicated 24/7 support
Why a mobile IP for automation
Scripts, bots and no-code workflows almost always run on servers or cloud services, so their requests start from datacenter IPs. Many sites treat these with suspicion: captchas, limited responses or pages that differ from what a real user sees.
A mobile IP is used every day by many real carrier customers through CGNAT: sites are far more careful before limiting it. With ProxyHub every proxy is a dedicated smartphone, so the IP you use is yours alone for the whole plan.
What you can automate
- Monitoring: prices, stock, rankings and competitors' pages, as on the Web scraping proxies page.
- Country checks: ads, landing pages and content as a smartphone user in Italy, the Netherlands, the UK or France sees them.
- Reports and dashboards: workflows that log in to the same accounts every day, with a stable IP and always from the same country.
- Site and app testing: checks of the mobile version, geolocation and response times from a real mobile network.
- No-code workflows: n8n and Make, to plug the proxy into your workflows without writing code.
Full control from code
- Rotation link: a GET request changes the IP and replies with the new address as soon as the change is complete. No key needed.
- API: with a key created under Settings → API you can list proxies, read IP and status, change IP, set protocol and automatic rotation, renew plans and check your balance. Docs and examples in ProxyHub API.
- Automatic rotation: an interval from 5 minutes to 24 hours, with no code.
How to set it up properly
- Set the proxy where requests start: in the script's HTTP library, at automated-browser launch or in n8n's and Make's HTTP node. Step by step in the n8n and Python guides.
- Separate workflows: a stable proxy for those that use accounts, one with rotation for those that collect data.
- Check the IP at start-up and log the IP, response code and timings of every round.
- Steady pacing and retries with growing waits: the full method is in Automation with proxies.
The terms of use of sites and platforms apply to automated workflows too.
Frequently asked questions
Can I control the proxies from my scripts?
Yes: with the API you can change IP, read the current IP, set protocol and automatic rotation and renew proxies. You create the key under Settings → API in the client area; the limit is 120 requests per minute per account.
Does the IP change while my workflow is running?
Only if you ask it to: from the button, the link, the API or with automatic rotation, if you've turned it on. During the change the connection drops for a few seconds, so requests in flight need repeating.
Does it work with n8n, Make and Playwright?
Yes: with any tool that supports an HTTP or SOCKS5 proxy with username and password. In n8n you set it in the HTTP Request node, in Make in the latest version of the HTTP module.
