Resources · Make integration

IP2Proxy Make integrationAutomate IP2Proxy with Make.

Need an IP address checked the moment it lands in one of your tools? The IP2Proxy Make integration gives you 1 action, Lookup IP Address, and no trigger. This page shows how to link your account and build a first scenario around it.

Try the IP2Proxy integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IP2Proxy Make integration do for you?

The IP2Proxy Make integration lets a Make scenario, the automation you build as a chain of modules, send an IP address to IP2Proxy and pass the answer to the next step. A module is one brick of that chain. IP2Proxy offers exactly one, Lookup IP Address, and it is an action.

Since IP2Proxy has no trigger, something else has to start the flow. Picture a sign-up form tool that records the visitor's IP: its trigger opens the scenario, Lookup IP Address checks the address, and a later module files the result next to the lead. The same pattern works for an order from an online store or for a row added to a spreadsheet by a support team.

Each item that moves between modules is called a bundle, and each run of a module on one bundle counts as one operation on your Make plan. One address checked means one operation for the lookup step.

Be clear on the limits. Make's own documentation for IP2Proxy is marked as limited: it lists the module but describes no fields and no connection prerequisites. Expect to discover the options inside the module itself once your connection exists. If a run fails, the Make troubleshooting guide covers the usual causes.

New to the editor? The Make training walks through the basics, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect IP2Proxy to Make?

  1. 01

    Add the module and open the connection window

    Put Lookup IP Address in your scenario, then click Create a connection. A connection is your IP2Proxy account linked to Make once, then reused in every scenario where you add the module.

  2. 02

    Name the connection

    Giving it a name is optional, yet it helps as soon as you run a test account and a production one side by side. Pick something you will recognize in a dropdown list.

  3. 03

    Authorize Make and save

    Follow what the window asks for: either an authorization page from IP2Proxy, or a key that IP2Proxy gives you to paste. Then click Save, and the module shows the connection as selected.

First scenario

Your first scenario with IP2Proxy

GoalWhen another app hands Make a new IP address, Make runs Lookup IP Address and passes the answer on.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. That first module comes from the app holding your IP addresses, such as a form or a sheet.

  2. 02

    Add the IP2Proxy action

    Click the + on the right of that first module, search for IP2Proxy and pick Lookup IP Address. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the address

    Fill the module fields by mapping the IP address from the previous module instead of typing one. Make offers the data it received, so you just click the right item.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and check what IP2Proxy returned.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then turn the scenario on. From then on, each new address flows through the lookup.

Modules

What the IP2Proxy module does

IP2Proxy gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

IP2Proxy1

Lookup IP Address

ActionIn the docs only

Lookup IP Address sends one IP address to IP2Proxy and hands the reply to the next modules, for example to fill a CRM field. It is the only IP2Proxy module in Make and handles one address per bundle.

When to use it
right after a module that captures a visitor's IP, such as a new form entry, so the answer is stored with the record.
Watch out
each address costs one operation, so run a single test with Run once before feeding it a long list.
Need help

Need help automating IP2Proxy with Make?

A person reads every message.

FAQ

IP2Proxy and Make: common questions

01Is the IP2Proxy Make integration free?
Yes, on the Make side. IP2Proxy is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations: each Lookup IP Address run on one bundle uses one. Whatever IP2Proxy charges for its own service is a separate matter this page does not cover.
02What do you need to connect IP2Proxy to Make?
An IP2Proxy account and a Make account. Make's documentation for this app gives no specific prerequisite, so the generic flow applies: add Lookup IP Address, click Create a connection, optionally name it, then either authorize Make on the IP2Proxy page or paste the key IP2Proxy provides, and click Save. The connection is stored once and reused by the module in any later scenario, so you only go through this step the first time.
03How does an IP2Proxy scenario start without a trigger?
It starts from another source. IP2Proxy has no trigger module in Make, so the scenario opens on a trigger from a different app, for example a form tool or a spreadsheet, or on Make's own schedule set on the first module. A new scenario checks every 15 minutes by default; the Free plan cannot go below 15 minutes, while paid plans can go down to 1 minute. Lookup IP Address then runs on each bundle that the first module delivers.
04What if the IP2Proxy module you need is missing in Make?
Look elsewhere, because this app has no Make an API Call module to reach other endpoints. Lookup IP Address is the only IP2Proxy module available, and Make flags its documentation for the app as limited. If your use case needs more than a single address lookup, check whether another app in the Make catalog covers it, or ask the team for help designing the flow around what exists today, starting from the module that already works.
05Should you use Make or n8n for IP2Proxy?
It depends on the tool your team already works in. IP2Proxy often has an n8n node as well, so the choice rarely hinges on this app alone. In Make, you get one action, Lookup IP Address, driven by a trigger from another app or by a schedule, and each run counts as an operation on your plan. Compare how each tool fits the rest of your stack, the apps you connect every day and who will maintain the scenarios, rather than this single integration.
Same platform

Other docs you might need on this stack.

Browse all integrations