Resources · Make integration

UserCheck Make integrationAutomate UserCheck with Make.

Can Make check an address before it lands in your CRM? The UserCheck Make integration adds 3 action modules to your scenarios. It is built for teams that collect sign-ups or leads, and this page takes you from the connection to a first working scenario.

Try the UserCheck integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the UserCheck Make integration do for you?

The UserCheck Make integration lets a Make scenario, the automation you build in Make, send an email address or a domain to UserCheck without any code. Each check is one module, a single brick of the scenario, and it works on the data another app hands over, such as a form entry or a new contact.

Screen sign-ups as they come in. A form or a store collects an address, and Check an email runs on it before the contact goes anywhere else. Sales or support then work from a list that has already been through UserCheck.

Look at company domains in a lead list. When a lead carries a website or a company domain, Check a domain sends it to UserCheck, so the domain is examined on its own, apart from any single mailbox.

Reach the rest of the API. Make an API Call uses the same connection to call any UserCheck endpoint that the two named modules do not cover.

Keep one limit in mind: the Make documentation for UserCheck lists the modules without describing them, and it warns that its content is AI-generated and may contain mistakes. Open each module after connecting to see what it really asks for. The same app may also have an n8n node; the n8n vs Make comparison sets out the criteria, and the Make training covers scenario basics if Make is new to you.

Connect

How do you connect UserCheck to Make?

  1. 01

    Copy your API key

    Log in to UserCheck and open the dashboard. In the API Keys section, generate a new key or pick one you already have, then copy the key shown on screen. You need an active UserCheck account for this.

  2. 02

    Open the connection window

    In your Make scenario, add a UserCheck module and click Create a connection. A connection is your UserCheck account linked to Make once, and every UserCheck module of the scenario reuses it afterwards.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several accounts share one Make workspace. Paste the API key you copied, or follow the instructions on screen, and save.

First scenario

Your first scenario with UserCheck

GoalWhen a new address arrives from another app, Make sends it to UserCheck with Check an email.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. UserCheck has no trigger, so the first module comes from the app that collects the addresses, such as your form tool.

  2. 02

    Add Check an email

    Click the + on the right of that first module, search for UserCheck and pick Check an email. Click Create a connection and paste your API key.

  3. 03

    Map the address

    In the module fields, map the email coming from the first module. Each bundle, one item passing from a module to the next, carries one address, so each one gets its own check.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Then read the bundles Check an email received and what UserCheck sent back before building further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the UserCheck modules do

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

UserCheck1

Check a domain

ActionIn the docs only

Hands a domain name to UserCheck and returns its answer to the scenario, so the company behind a lead is looked at before anyone spends time on it.

When to use it
a lead form asks for a company website and you want that domain examined on its own, without a specific mailbox.
Watch out
the doc gives no field list for this module, so open it after connecting and map exactly what it asks for.
UserCheck2

Check an email

ActionIn the docs only

Sends one email address to UserCheck and brings the result back into your scenario, ready for the next module to use. It runs once per bundle, so a batch of ten addresses means ten checks.

When to use it
right after a sign-up form or a new contact, before the address is copied into your CRM or newsletter tool.
Watch out
each check is an operation on your Make plan, so place it only where an address really needs one.
UserCheck3

Make an API Call

ActionIn the docs only

Gives you access to any endpoint of the UserCheck API with the connection you already set up, which covers whatever the two named modules leave out.

When to use it
the UserCheck API offers a request that neither Check an email nor Check a domain handles, and you would rather not build the authentication yourself.
Watch out
this module expects you to know the endpoint and its parameters from the UserCheck API documentation.
Need help

Need help automating UserCheck with Make?

A person reads every message.

FAQ

Questions about UserCheck and Make

01Is the UserCheck Make integration free?
Yes, on the Make side. UserCheck is a standard app, available from the Free plan, which allows 2 active scenarios, runs at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. UserCheck itself needs an active account with an API key; its own subscription is described on the UserCheck pricing page.
02What do you need to connect UserCheck to Make?
An active UserCheck account and an API key. Log in to UserCheck, open the API Keys section of the dashboard, generate a key or pick an existing one, and copy it. In Make, add any UserCheck module, click Create a connection, give the connection a name if you like and paste the key. That single connection then serves Check an email, Check a domain and Make an API Call, so you only go through these steps once per account.
03Can UserCheck start a Make scenario in real time?
No, because UserCheck has no trigger module in Make. The scenario has to start from something else: a trigger from the app that collects the addresses, such as a form or a store, or the schedule on the first module, which is every 15 minutes by default on a new scenario. An instant trigger of another app, called by a webhook as soon as something happens, is also a valid starting point. UserCheck then runs as an action in the middle of the flow.
04What if a UserCheck module is missing in Make?
Use Make an API Call. It reaches any endpoint of the UserCheck API with the connection you already created, so no new authentication is needed. You will have to read the UserCheck API documentation to know the endpoint and its parameters. Also keep in mind that the Make doc for this app warns it is AI-generated and may contain mistakes: when a module behaves differently from what you expected, check the vendor documentation or ask UserCheck directly.
05Should you use Make or n8n for UserCheck?
It depends on the tool your team already runs. In Make, UserCheck comes with 3 ready modules and a guided connection by API key, which suits someone building their first scenario. The same app often has an n8n node too, so the choice rests on which editor you prefer, where your other automations live and who will maintain them. Compare both on these criteria rather than on the app itself, since UserCheck is reachable from either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations