What’s inside?
Before you get started going through this build, here’s a little on how I structured this article. Unlike previous content, this is a combination of short videos and text guiding you on how to recreate this automation on your own.
I figured a combo would be easier to digest and not as long as the other. Now that that’s over with, you can get to reading.
Know Your Customer - KYC
KYC is simply a way for you to verify the identity of your customers. It’s majorly a requirement in the financial and other related sectors. There are a ton of platforms that can help you handle identity verifications for your users. A couple of them include Dojah, Smile Identity, Identity Pass etc.
For a lot of these platforms, you can integrate with them by implementing their APIs while some of them also have no-code tools that allow you manually verify your users. In this build, we’re going to be building an automation to handle the verification.
What we’re building
We’re building a simple three-step automation on Make to collect user data, verify that data and then update their record based on the results of the verification.
Toolstack
The tools we’re going to be using are:
- Make (Formerly known as Integromat)
How it works
A user fills out their information on the application or a form connected to a database (which in this case is Airtable), this kicks of an automation in Make to verify the details provided and then update the verification status of the record on the database based on the results.
Checklist
Set up your Airtable base
Add your modules
Test your scenario
Let’s build
Set up your Airtable base
Start by creating a base on your Airtable account. Create a table and add fields for all the information you are collecting from the user.
Add your first module
Your first module is for a trigger on Airtable. Choose the Airtable app and then select a trigger for watching newly created records.
The Identity Pass module
To complete setting up your scenario, you’ll need access to the Identity Pass app on Make. You can request access here. Zapier coming soon.
Complete your scenario and test
Complete your scenario by adding the appropriate module for Identity Pass and an action module to update the created record on Airtable. I forgot to add this in the video but you should make sure you are setting up a filter to only update the record to the Verified status on Airtable if the status returns as VERIFIED on the Identity Pass module.
More on filtering below.
Add some extra functionalities
You can improve your KYC setup by adding additional filters to your scenario. You can add filters to only update a record to the ‘Verified’ status when all of certain conditions are met. Here’s an example:
A user has provided a valid NIN which when looked up turned out to be verified. But you want to be sure that the names or DOB they provided match what is returned when the NIN was looked up.
To do this, you’ll set up filters to only update a record to Verified when the the first name and last name match the names returned via the Identity Pass Module and when the verification status returns as Verified. Take a look at the steps below.
Add a router between the last two modules
Routers are flow control tools in Make that allow you create different paths for your scenario. We’re adding a router in this case so we can create two paths; one for when we want to update the user’s verification status to Verified and another to update it to Not Verified.
Click on the little spanner icon to add a router.
Set up a filter for the first path
Click on the same spanner icon but between the router and Airtable to set up a filter.
Set up the conditions for the filter
The first condition is for when the first name on Airtable for the very first module is equals to the first name on the NIN data in the Identity Pass module. Make sure that you are selecting the equals to option that is case insensitive. This way the filter will still get applied even if both values are not the same cases.
Click on the button to add an AND rule and repeat the condition setup but for the last name. Do this for as many conditions that you want set up in that filter.
The very last condition should be that the verification status in the Identity Pass module is equals to VERIFIED.
If all of these conditions are met, the action in the Airtable module will run and update the record’s verification status to Verified.
Add a second path
Click on the router and a module for another path will appear. Choose Airtable for this module and select the action to update a record.
Set up the filter
Add a filter between the router and the Airtable module for the second path.
Add the condition
The condition for the second path is simple. If the verification status from the Identity Pass module is not equals to VERIFIED, then we want to update the record’s status on Airtable to Not Verified.
And that’s it.
If you liked this article, make sure to share it with someone.
If you’d like to leave feedback, you can tweet at me or send a DM.
Need help with the build or anything no-code related? Send an email.