Resources · Make integration

AddressVerify Make integrationAutomate AddressVerify with Make.

Want every new address checked before it lands in your tools? The AddressVerify Make integration gives you 2 action modules, which, going by their names, handle an address written on a single line and one split over several lines. This page walks you through the connection, a first scenario and the gaps to know about.

Try the AddressVerify integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AddressVerify Make integration do for you?

The AddressVerify Make integration lets a Make scenario (the automation you build, a chain of modules) send an address to AddressVerify for verification, without writing code. It has no trigger of its own: another app, or a schedule, starts the scenario, and AddressVerify handles the checking step in the middle.

Clean shipping addresses from an online store. A new order comes in through your store app, and Verify Single Line Address checks the address the customer typed in one field before anyone packs the parcel.

Structured addresses from a CRM or a spreadsheet. When street, city and postal code sit in separate columns, Verify Multi Line Address is, going by its name, the module built for that shape, so you keep the parts instead of gluing them together.

A checkpoint in a signup flow. Put the verification between a form tool and your database, and only verified entries move on. If forms are your starting point, the 123FormBuilder Make integration page shows that side.

What Make does not give you here: Make itself flags the documentation for AddressVerify as limited, because little public information exists about the app. Field names and responses are not described, so test with a real address before relying on the result. Our Make review covers the editor in general, and if you also look at n8n, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect AddressVerify to Make?

  1. 01

    Add an AddressVerify module

    In your scenario, click the +, search for AddressVerify and pick one of its two modules. Make then asks for a connection, which is your AddressVerify account linked to Make once and reused by both modules.

  2. 02

    Create the connection

    Click Create a connection. You can give it a name, which helps when a teammate or a second account shows up later. Then either authorize Make on the AddressVerify page or paste the key AddressVerify gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and every AddressVerify module in any of your scenarios can pick it from the list without asking again.

First scenario

Build your first scenario with AddressVerify

GoalWhen a new address reaches another app you use, Make sends it to AddressVerify with Verify Single Line Address.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Choose the app where addresses arrive, such as your store or form tool.

  2. 02

    Add the verification module

    Click the + on the right of that first module, search AddressVerify and pick Verify Single Line Address. Create the connection if you have not done it yet.

  3. 03

    Map the address

    In the module fields, map the address coming from the first module. Each bundle, meaning one item passing from one module to the next, carries one address here.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open the bundles each module received to see what AddressVerify sent back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What AddressVerify can do in Make

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

AddressVerify1

Verify Multi Line Address

ActionIn the docs only

This action sends AddressVerify an address that is already split into several lines, the way CRMs and spreadsheets often store it. Its name suggests you keep your columns instead of merging them.

When to use it
your addresses come from a system with separate fields for street, city and postal code, and joining them would add a text step for nothing.
Watch out
Make publishes no description of this module's fields, so run it once on a known address and read the bundle before you map its output.
AddressVerify2

Verify Single Line Address

ActionIn the docs only

Pick this one when the whole address lives in a single text field, like the box a shopper fills in at checkout. It passes that one string to AddressVerify for checking.

When to use it
order forms, chat messages or imports where nobody split the address into parts, and splitting it yourself would be guesswork.
Watch out
the response format is not documented on the Make side, so test with Run once and look at what comes back before building filters on it.
Need help

Need help automating AddressVerify with Make?

A person reads every message.

FAQ

AddressVerify and Make: common questions

01Is the AddressVerify Make integration free?
Yes, on the Make side. AddressVerify is a standard app, so it is available from the Free plan, like the 3000+ standard apps Make offers on every plan. The Free plan limits you to 2 active scenarios and a minimum of 15 minutes between two scheduled runs, with 5 minutes of execution at most. Paid plans lower the interval to 1 minute and lift the cap on active scenarios. Your AddressVerify account is a separate matter: check its own terms directly with AddressVerify.
02What do you need to connect AddressVerify to Make?
An AddressVerify account and a Make account. The Make documentation lists no specific prerequisite for this app and does not describe the exact connection method. In practice you add an AddressVerify module, click Create a connection, optionally name it, then authorize Make or paste the key AddressVerify provides, and click Save. The connection is then shared by both modules in all your scenarios. If the window asks for something you cannot find in your account, stop there and check with AddressVerify rather than guessing.
03Can the AddressVerify Make integration start a scenario on its own?
No. AddressVerify has no trigger module in Make, only 2 actions, so it always sits after another module. You can start the scenario with a trigger from the app where addresses arrive, instant if that app calls Make through a webhook, scheduled if Make polls it. You can also rely on the schedule of the first module, set to every 15 minutes by default and never below 15 minutes on the Free plan.
04What if an AddressVerify module you need is missing in Make?
Make offers only the two verification modules for AddressVerify, and this app has no Make an API Call module to reach other parts of its API. Make also marks its documentation for the app as limited. If you need something the two modules do not cover, look for another app that fits the job, or ask the team behind our Make agency to review the case with you before you build around a gap.
05Should you use Make or n8n for AddressVerify?
It depends on what you already run. On Make, AddressVerify comes with 2 action modules and a visual editor where you test each step with Run once. Many apps also have an n8n node, so first check whether AddressVerify has one. The comparison page linked in the section above sets out the criteria side by side, without declaring a winner. Pick the tool where the rest of your address workflow already lives, so the verification step stays next to it.
Same platform

Other docs you might need on this stack.

Browse all integrations