IdentityCheck Zapier integrationAutomate IdentityCheck with Zapier.
The IdentityCheck Zapier integration gives you 3 actions, 0 triggers and 0 searches. Another app starts the Zap, IdentityCheck then opens a verification for the person, by email, by SMS or directly. It works on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the IdentityCheck Zapier integration actually does
It lets a Zap (an automation you build once on Zapier, which runs every time a starting event happens) open an identity verification in IdentityCheck without anyone copying names and emails by hand. The starting event always lives in another app, because IdentityCheck offers no way to start a Zap itself.
Three outcomes, each tied to one action. A verification link in the person's inbox or on their phone: Create Verification by Email/SMS opens the check and sends the link through the channel you pick. A direct verification opened from an email address, with Create Verification. A Tranche 2 verification built from a first name, a last name and an email, with Create Tranche 2 Verification.
Think of a lending desk where every new contact in the CRM must be checked before a file moves. Today someone opens IdentityCheck, retypes the details, sends the link. With the Zap, the contact lands and the link goes out. Nobody retypes anything (and nobody forgets the third contact of a busy afternoon).
Now the honest part. Zapier cannot react to IdentityCheck: there is no trigger, so a finished or failed verification will not start anything on its own. There is no search either, which means a Zap cannot look up a verification that already exists. And the integration only creates: it does not update, cancel or delete a check.
If you are weighing platforms, the IdentityCheck Make integration page covers the same app on Make, and the Make vs Zapier comparison sets the two tools side by side.
The Zapier words you will meet here
Eight terms. Read them once, the rest of the page uses them without explaining again.
- Zap
- What you build on Zapier: one trigger from another app, then one or more actions, here the IdentityCheck verification, that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. IdentityCheck has none, so it comes from another app.
- Action
- What the Zap does once started: the step that writes, sends or creates something for you. All three IdentityCheck operations are actions.
- Task
- What Zapier bills you for. Each verification IdentityCheck actually creates through your Zap is one task, and your plan's allowance is a count of those.
- Polling vs instant trigger
- Polling: Zapier checks the app on a timer and keeps what is new. Instant: the app calls Zapier the moment the event happens.
- Filter
- A checkpoint between the trigger and IdentityCheck: the Zap only goes on to create a verification when the incoming record meets your condition.
- Connection
- The link between your IdentityCheck account and Zapier, set up once. All three verification actions then reuse it in any Zap.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a verification Zap really costs
IdentityCheck is not a premium app, so it runs on the free plan. The bill is counted in tasks, and only successful actions count.
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- TriggerNever billed
- Each IdentityCheck actionOne task when it succeeds, none when it fails
- Filter or second actionMulti-step Zap, paid plan required
The trigger never costs a task, however often Zapier checks the starting app. Each IdentityCheck action that goes through costs one; an action that fails costs nothing. The catch: the free plan stops at two steps. Add a filter to keep only some contacts, or a second action, and the Zap becomes multi-step, which needs a paid plan. On the 100 free tasks, a Zap with one IdentityCheck action covers up to 100 verifications a month.
Connect IdentityCheck to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an IdentityCheck account first, plus access to anything you do not own yourself and want the Zap to touch.
- 02
Find IdentityCheck
Type IdentityCheck in the dialog, pick it from the results, then click Add connection. A new browser tab then opens on the IdentityCheck sign-in page.
- 03
Sign in and grant access
Log in to IdentityCheck in that tab and allow Zapier to use the account. The connection is then saved, and every IdentityCheck step in any Zap reuses it.
Your first Zap: a HubSpot contact gets an SMS or email check
GoalEach new HubSpot contact with a phone number receives an IdentityCheck link, without anyone opening IdentityCheck.
- 01
Build: set the starting event
Create a Zap and choose HubSpot with New Contact as the trigger. Testing it brings back the three most recent contacts, so you map fields on a real record.
- 02
Add the filter
Click the plus icon, choose Filter, then set the field (Phone Number), the rule (exists) and check it against the test record. This step makes the Zap multi-step, so a paid plan.
- 03
Add the IdentityCheck action
Add a step, choose IdentityCheck and Create Verification by Email/SMS. Fill Delivery Methods, the one required field, then map the contact details from HubSpot.
- 04
Test the action
Run the step once and read what came back. A real verification is created at this point, so test on a contact you control rather than a customer.
- 05
Publish
Click Publish to switch the Zap on. From then on, only contacts created after publishing get a link: the Zap does not go back through older ones.
The 3 IdentityCheck actions
IdentityCheck gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Verification
ActionIn Zapier“Create direct verification”
Opens a direct verification in IdentityCheck from an email address, with no extra delivery choice to make. It asks for two addresses: Email and Email User.
Create Tranche 2 Verification
ActionIn Zapier“Create Tranche 2 Verification”
Starts the Tranche 2 flavor of a verification, built from the person's identity rather than from an address alone. First Name, Last Name and Email are all mandatory.
Create Verification by Email/SMS
ActionIn Zapier“This action allows you to create a IdentityCheck verification and send the verification link via Email and/or SMS”
Creates the check and sends the person their verification link, by email, by SMS or both. The only required field is Delivery Methods.
When an IdentityCheck Zap breaks
Zapier attaches no help article to IdentityCheck, and no app-specific limit is documented. What breaks comes from how Zaps work in general.
Four cases cover most of the surprises. If the Zap still misbehaves after checking them, the Zapier troubleshooting page is the next stop.
Contacts from before the Zap get nothing
A Zap only reacts to events after it is switched on. Contacts that already existed never receive a link; sending to them is a separate job.A big import gets held back
Import a large batch into the starting app and the trigger suddenly returns a huge pile. Zapier's flood protection can hold that batch back instead of firing a verification for each.The same contact does not fire twice
On a polling trigger, Zapier remembers what it has already seen. Editing an old contact will not send a second verification on its own.A required field arrives empty
Email, First Name, Last Name or Delivery Methods left blank stops the action. A failed action costs no task, but the person gets no link either.
Need help automating IdentityCheck with Zapier?
A person reads every message.
