Resources · Make integration

Loqate Make integrationAutomate Loqate with Make.

Tired of bounced emails and parcels sent to the wrong street? The Loqate Make integration gives you 5 action modules to check emails, phone numbers and addresses inside your automations. This page connects your account and walks you through a first scenario that cleans each new contact.

Try the Loqate integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Loqate Make integration do for you?

The Loqate Make integration lets a Make scenario (the automation you build, a chain of steps called modules) send contact data to Loqate and get a verdict back. You check an email, a phone number or a list of addresses at the moment the data enters your tools, with no code and no copy and paste.

Clean leads before they reach sales. When a form tool or an ad platform sends a new lead, Validate a Single Email and Validate a Phone Number check both fields before the contact reaches your CRM. Your reps stop calling numbers that do not exist.

Tidy an imported list in one pass. A trade show file or an old export can go through Batch Email Validation, up to 100 emails per call, so your next campaign starts from a list you trust.

Ship to real addresses. An online store can send its delivery addresses to Batch Address Validation, which handles up to 500 international addresses per call, before orders reach the warehouse.

Limits worth knowing: Loqate has no trigger in Make, so your scenario always starts from another app or from a schedule. What the 5 modules do not cover can go through Make an API Call, with the same connection. The same app often has a node in n8n too; the n8n vs Make comparison helps you pick. For plans and credits, read Make pricing, and if you want a hand, the Make agency team builds these flows.

Connect

How do you connect your Loqate account to Make?

  1. 01

    Generate your Loqate API key

    You need an active Loqate account first. In the Loqate dashboard, open API Keys in the menu, click Generate API Key, then copy the key shown on screen. Keep it at hand for the next step.

  2. 02

    Add a Loqate module in Make

    In your scenario, add any Loqate module and click Create a connection. A connection is your Loqate account linked to Make once, then reused by every Loqate module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Loqate into the connection window, or follow the on-screen instructions, then save. Make now lists your connection in the module, and every other Loqate module you add can pick the same one.

First scenario

Build your first scenario: check every new lead

GoalWhen a new lead comes in from another app, Make asks Loqate to check the email and the phone number before the contact moves on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your leads land, a form tool or a CRM, and its module that returns new entries.

  2. 02

    Add Validate a Single Email

    Click the + on the right of that first module, search Loqate and pick Validate a Single Email. Select your connection, then map the email field coming from the lead.

  3. 03

    Add Validate a Phone Number

    Add one more module with the +: Validate a Phone Number. Map the phone field of the same lead. Each lead is a bundle, one item that flows from module to module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, and check that both answers match what you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation, the unit Make bills on your plan.

Modules

What each Loqate module does

Loqate gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Loqate1

Batch Address Validation

Action

In Make“Verifies a batch of up to 500 international addresses.”

Sends a whole list of addresses to Loqate in one call and gets each one checked, up to 500 international addresses per batch. You get cleaner shipping data without handling addresses one by one.

When to use it
an online store or a mailing team has a pile of addresses to verify before orders or letters go out.
Watch out
past 500 addresses, split your list into several batches.
Loqate2

Batch Email Validation

Action

In Make“Verifies up to 100 emails per batch.”

Checks a group of email addresses in a single request, up to 100 per batch, so a list gets cleaned before you send anything to it. You spot the dead addresses before your campaign does.

When to use it
you imported contacts from an event or an old tool and want to know which emails still work.
Watch out
a list longer than 100 emails needs several batches.
Loqate3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the full Loqate API from your scenario, using the connection you already set up. Anything the four other modules do not offer can still be reached this way, by calling the endpoint you need.

When to use it
you need a Loqate feature that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Loqate API documentation open while you set it up.
Loqate4

Validate a Phone Number

Action

In Make“Validates a phone number.”

Tells you whether one phone number is valid, so your team only calls or texts numbers that can actually ring. It works on one number at a time, right when a contact enters your tools.

When to use it
a lead form or a signup flow collects phone numbers and sales will pick up the phone next.
Watch out
map the phone field itself, not a field that mixes the name and the number.
Loqate5

Validate a Single Email

Action

In Make“Validates a single email.”

Checks one email address and returns Loqate's answer, so a typo or a fake address gets caught before it lands in your CRM or your newsletter tool. One contact, one check.

When to use it
each time a person signs up, buys or fills a form, and you want the address confirmed on the spot.
Watch out
for a whole file of contacts, Batch Email Validation uses fewer calls.
Need help

Need help automating Loqate with Make?

A person reads every message.

FAQ

Loqate and Make: common questions

01Is the Loqate Make integration free?
Yes on the Make side: Loqate is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) go down to a 1 minute interval, remove the cap on active scenarios and count usage in credits per month. Loqate itself is a separate subscription: you need an active Loqate account and an API key, and the Loqate pricing page gives its terms.
02What do you need to connect Loqate to Make?
You need an active Loqate account and an API key. In the Loqate dashboard, open API Keys, click Generate API Key and copy the key shown. In Make, add a Loqate module, click Create a connection, give it a name if you like, paste the key and save. That single connection then serves all 5 Loqate modules, including Make an API Call, so you only set it up once per Loqate account.
03Does Loqate trigger Make scenarios in real time?
No, because Loqate has no trigger module in Make: all 5 modules are actions. The scenario starts from something else. The usual choice is the trigger of the app where your data arrives, like a form or a CRM, so Loqate checks each new contact as it comes through. You can also start the scenario on a schedule set on its first module, every 15 minutes by default, or from a Make webhook that another tool calls.
04What if a Loqate module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Loqate API from your scenario, with the same connection as the other modules, so a feature without its own module is still within reach. For large volumes, keep the batch limits in mind: Batch Address Validation takes up to 500 addresses per call and Batch Email Validation up to 100 emails, so split bigger lists into several calls and map each batch in turn.
05Should you use Make or n8n for Loqate?
It depends on the tool your team already uses. Loqate has native modules in Make, including Make an API Call for the rest of its API, and the same app often has a node in n8n too. If your other automations already live in Make, keeping Loqate there means one editor and one place to test with Run once. If they live in n8n, stay there. The choice rests on your existing setup, not on Loqate.
Same platform

Other docs you might need on this stack.

Browse all integrations