Blinq + StackGo
Run compliance from inside Blinq. Checks start from a record and the result lands back on the client.
Blinq publishes 2 trigger events and 0 actions on its public Zapier listing. That is what a StackGo connector would be built on.
Also listed under Client onboarding
Blinq digital business cards allow you to instantly share who you are, with anyone, wherever you go.
Description supplied by Blinq.
What starts a check
You do not open StackGo. A change in the system starts the work, and the system stays your source of truth.
- Updated Contact
- New Contact
What StackGo puts back on the record
A Blinq connector would write the outcome, the status and a link to the result onto the record by default. These are the fields StackGo can write on the systems it connects to today.
- Verification status
- Risk rating
- Last checked
- Report link
- Verified name
- Date of birth
- Document checked
- Screening result
- Beneficial owners
- Form responses
- Verification report (PDF)
Personal fields are off by default. What goes back to your CRM explains the default; what each field holds is set out in what “integrates with” actually means.
Common questions about Blinq
What is Blinq used for?
Blinq digital business cards allow you to instantly share who you are, with anyone, wherever you go.
Which Blinq events can start a compliance check?
“Updated Contact”, “New Contact”. These are Blinq’s own trigger names from its public Zapier listing. StackGo does not connect to Blinq yet, so they show where a connector would start.
Questions taken from what people actually search in Australia. We answer only the ones our own data answers.
Blinq is made by blinq.me. We are not affiliated with them.
Want Blinq connected?
Requests decide the build order. Tell us and we will tell you where it sits.
Request this integrationReady to make onboarding minutes, not hours?
Start free and run your first check today, or book a demo and we will walk you through it.