Resources · Make integration

REST Countries Make integrationAutomate REST Countries with Make.

Got a country code in a spreadsheet, a form or a CRM and need the matching country record? The REST Countries Make integration gives you 2 modules: one search by country code and one open API call. This page shows you how to link your API key, then build and test a first scenario.

Try the REST Countries integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the REST Countries Make integration do?

The REST Countries Make integration lets a Make scenario (the automation you build, a chain of modules) look up a country from its code and hand the result to your other apps. You add the REST Countries module after the step that holds the code, and Make fetches the matching country without any code on your side.

Enrich new leads with their country. A form or a CRM passes a country code to your scenario; Search By Country Code returns the country, and the next module writes it back to the contact. Your sales team reads a real country name instead of a bare code.

Check codes before they spread. An order or a spreadsheet row carries a code someone typed by hand. When the search returns zero bundles (a bundle is one item passed from a module to the next), you know the code is wrong and can route the row to a review step.

Reach what the search does not cover. Make an API call sends any request to the REST Countries API with the same connection, so you are not limited to the code lookup.

Know the limit before you start: Make states that it cannot provide complete documentation for REST Countries, because too little public information exists about the app. Expect to test each module with Run once rather than rely on the docs. New to the editor? The Make training walks through the basics, and the n8n vs Make comparison helps if you are still picking a tool. The Make pricing page explains how operations are counted.

Connect

How do you connect REST Countries to Make?

  1. 01

    Copy your API key from REST Countries

    Log in to your REST Countries account and open API Keys. Copy the key value and keep it somewhere safe: Make will ask for it once, and every REST Countries module of your scenarios will reuse it.

  2. 02

    Open the connection window in Make

    Add a REST Countries module to your scenario and click Create a connection. A connection is your REST Countries account linked to Make. The Connection name field is optional, but a clear name helps when you run several accounts.

  3. 03

    Paste the key and save

    Paste the key into the API key field, then click Save. The module can now query REST Countries, and the same connection shows up in the list the next time you add one of its modules.

First scenario

Your first scenario with REST Countries

GoalWhen another app hands over a country code, Make looks up the matching country in REST Countries.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. REST Countries has no trigger, so this first module comes from the app that holds your codes.

  2. 02

    Pick the app that holds the codes

    Search your form tool, CRM or spreadsheet app by name, choose the module that reads new records and link its account. Each record it returns becomes one bundle for the rest of the flow.

  3. 03

    Add Search By Country Code

    Click the + on the right, search REST Countries and pick Search By Country Code. Choose your connection, then map the code coming from the previous module into the module.

  4. 04

    Test with Run once

    Click Run once and read the bundles each module received. If the search returns nothing, check the code that came from the first app.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default, the minimum on the Free plan) and switch the scenario on. Make then checks for new records on that clock.

Modules

What can REST Countries do in Make?

REST Countries gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

REST Countries1

Search By Country Code

SearchIn the docs only

Turns a country code into the matching country record from REST Countries, ready for the next module to use. As a search module, it can return zero, one or several bundles.

When to use it
a new contact, order or sheet row arrives with a code, and you want the full country next to it before it lands in your CRM.
Watch out
a zero result usually means a mistyped code, so add a filter or a review branch instead of letting the empty run pass silently.
REST Countries2

Make an API call

ActionIn the docs only

Opens the rest of the REST Countries API to your scenario: you write the request yourself and Make sends it with the connection you already set up. It is the escape hatch when the code search is not the lookup you need.

When to use it
pick it only once you have confirmed the request you want exists in the REST Countries API.
Watch out
Make publishes little documentation for this app, so test each request with Run once before you switch the scenario on.
Need help

Need help automating REST Countries with Make?

A person reads every message.

FAQ

Questions about REST Countries and Make

01Is the REST Countries Make integration free?
Yes, REST Countries is a standard app, so it works from the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle counts as one operation, which is what Make tracks on your plan.
02What does it take to connect REST Countries to Make?
You need a REST Countries account and its API key. Log in to REST Countries, open API Keys and copy the key. In Make, add a REST Countries module, click Create a connection, name the connection if you like, paste the key into the API key field and click Save. Both modules then reuse that connection, so you only paste the key once for all your scenarios. If you run several REST Countries accounts, create one connection per account.
03Does REST Countries trigger a Make scenario in real time?
No, REST Countries has no trigger module, so it never starts a scenario on its own. The scenario starts on a trigger from another app, such as a form or a CRM that sends new records, or on the schedule you set on the first module, every 15 minutes by default. REST Countries then acts in the middle of the flow, when a code reaches the Search By Country Code module.
04What if a REST Countries Make module is missing?
It depends on the request. The Make an API call module reaches any endpoint of the REST Countries API with the same connection, so it covers what Search By Country Code does not. Make also warns that its documentation for REST Countries is incomplete, because little public information exists about the app. Test each request with Run once and read the returned bundles before you rely on them in a live scenario.
05Should you use Make or n8n for REST Countries?
It depends on what you already run. On the Make side, REST Countries comes with a country code search and an open API call, set up through a visual editor where you test each step with Run once. Before choosing n8n, check whether it offers a node for REST Countries, since this page only covers the Make app. If your other automations already live in one of the two tools, keeping REST Countries there is usually the simpler call.
Same platform

Other docs you might need on this stack.

Browse all integrations