Resources · Make integration

IdentityCheck Make integrationAutomate IdentityCheck with Make.

Start an IdentityCheck verification the moment another app says it is time. The IdentityCheck Make integration gives you 2 action modules and no trigger. This guide shows how to link your API key, then walks you through a first scenario you can test right away.

Try the IdentityCheck integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IdentityCheck Make integration do for you?

The IdentityCheck Make integration lets a Make scenario (the automation you build in Make, a chain of bricks called modules) open verifications in your IdentityCheck account without anyone copying data by hand. Another app supplies the person's details, and IdentityCheck receives the request through your connection.

Onboarding that starts itself. When a new client lands in your CRM or your signup form, the scenario passes their details to Create a Verification. Your team no longer has to open IdentityCheck and retype anything.

One request path for every channel. Web forms, spreadsheets and support tools can each feed the same Create a Verification module, so every check is opened the same way, whatever the source.

Reach the rest of the API. For any request the listed module does not cover, Make an API Call talks to the IdentityCheck API with the connection you already set up.

Know the limits before you build. IdentityCheck has no trigger in Make, so a scenario cannot wake up on its own when something changes inside IdentityCheck: it starts from another app or from a schedule. The official Make documentation for this app is also marked as AI-generated, so confirm important details with IdentityCheck. Weighing the other big tool? Read n8n vs Make, and if a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect IdentityCheck to Make?

  1. 01

    Create an API key in IdentityCheck

    In IdentityCheck, open Account, then Users, and add a user with the developer permission. Accept the email invitation, sign in with that user, go to API Keys, name a key and click Save. Copy the key shown on screen.

  2. 02

    Add the module and open the connection

    In your Make scenario, add an IdentityCheck module and click Create a connection. A connection is your IdentityCheck account linked to Make once, then reused by both modules. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied from IdentityCheck, or follow the instructions Make shows on screen, then confirm. The connection now appears in the module, and every later IdentityCheck module can pick it from the list.

First scenario

Your first scenario with IdentityCheck

GoalWhen a new client arrives in another app, Make opens a verification in IdentityCheck.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since IdentityCheck has no trigger, pick the app where new clients appear, such as your form tool or CRM.

  2. 02

    Set up the starting module

    Connect that app and fill its fields. Once the connection exists, Make lists what it can read, so you pick the right form or list instead of typing its name. Each new client becomes one bundle, one item passed to the next module.

  3. 03

    Add Create a Verification

    Click the + on the right of the first module, search IdentityCheck and pick Create a Verification. Select your connection, then map the client details from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, and check in IdentityCheck that the verification really appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks for new clients. A new scenario runs every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Modules

What the IdentityCheck modules do

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

IdentityCheck1

Create a Verification

ActionIn the docs only

This module opens a new verification in your IdentityCheck account from data your scenario already holds, so the check starts without a manual step.

When to use it
right after a new customer, tenant or applicant shows up in another app and needs to be checked before you go further with them.
Watch out
it runs once per bundle, so a starting module that returns several new rows opens as many verifications and uses as many operations, the unit Make counts on your plan.
IdentityCheck2

Make an API Call

ActionIn the docs only

Here you get access to any endpoint of the IdentityCheck API, reusing the same connection as Create a Verification, so you are not limited to the one ready-made action.

When to use it
when your process needs a request that no listed module offers and the IdentityCheck API documentation describes the endpoint.
Watch out
the documentation only names the verification.create scope for the key, so check with IdentityCheck which scope another request needs.
Need help

Need help automating IdentityCheck with Make?

A person reads every message.

FAQ

IdentityCheck and Make: common questions

01Is the IdentityCheck Make integration free?
Yes, on the Make side. IdentityCheck is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between 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 count usage in credits, meaning operations, each month. Your IdentityCheck subscription is separate: you still need an active IdentityCheck account, and its own pricing page tells you what that costs.
02What do you need to connect IdentityCheck to Make?
You need an active IdentityCheck account and an API key. The key is created inside IdentityCheck: add a user with the developer permission under Account and Users, activate that user from the invitation email, sign in with it, then create a key in the API Keys section with the verification.create scope and save it. In Make, add an IdentityCheck module, click Create a connection, give it a name if you want, and paste the key. That one connection then serves both modules.
03Can IdentityCheck start a Make scenario in real time?
No. IdentityCheck has no trigger module in Make, neither scheduled nor instant, so nothing inside IdentityCheck can launch a scenario. You start the flow elsewhere: put a trigger from another app first, such as a form or CRM, and let Make check it on the scenario schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan. The IdentityCheck modules then run as actions later in the chain, each time a bundle reaches them.
04What if the IdentityCheck module you need is missing in Make?
Use Make an API Call. It is listed for IdentityCheck in Make, and it lets the scenario call any endpoint of the IdentityCheck API with the connection you already created, so you are not stuck with Create a Verification alone. Check that your API key carries the scope the request needs. Keep in mind that Make labels its IdentityCheck documentation as AI-generated, so when a detail matters, confirm it with the IdentityCheck documentation or their team before you rely on it.
05Should you use Make or n8n for IdentityCheck?
It depends on the tool your team already builds in. On Make, IdentityCheck offers 2 modules: Create a Verification and Make an API Call, available from the Free plan. Many apps also have an n8n node, so if you work in n8n, check whether IdentityCheck is available there before choosing. Decide on what each tool actually offers for this app and on where your other automations live, rather than on the brand. The n8n vs Make comparison linked above goes through the criteria in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations