Open Didit on Zapier
Browse triggers, actions, and ready-made templates on the Zapier marketplace.
What You Get
Create Sessions
Trigger verification sessions from form submissions, CRM events, or any Zapier-connected app.
Real-Time Webhooks
Receive instant status updates (Approved, Declined, In Review, etc.) as Zapier triggers.
Retrieve Results
Fetch full session details — ID data, liveness scores, AML hits — on demand.
Prerequisites
| Requirement | Details |
|---|---|
| Didit account | Sign up at business.didit.me |
| API Key | From Didit Console → API & Webhooks |
| Workflow ID | From Didit Console → Workflows (the workflow you want to trigger) |
| Zapier account | Free or paid — zapier.com |
How It Works
Connect Didit to Zapier
In Zapier, search for Didit and connect your account using the API Key from your Didit Console.
Set Up a Trigger
Choose what starts your Zap. This can be a Didit trigger or any other app:
| Trigger Source | Example |
|---|---|
| Didit webhook | Session status changes to “Approved” |
| Google Forms | New form submission → create a verification session |
| HubSpot | New contact created → trigger KYC |
| Stripe | New customer → verify identity before payout |
| Typeform | Onboarding form completed → start verification |
Add a Didit Action
Use one of the available Didit actions:Create Verification Session
- Provide the Workflow ID of the verification flow to execute
- Set a Callback URL for redirect after completion
- Pass Vendor Data (e.g., user email or internal ID) to link the session to your records
- The action returns a
verification_url— share it with the user
- Pass a
session_idto fetch the full verification result - Access ID data, liveness scores, AML results, and more
React to Results
Add downstream actions based on the verification outcome:
| Status | Suggested Action |
|---|---|
"Approved" | Update CRM, grant platform access, send welcome email |
"Declined" | Flag in database, notify compliance, send rejection email |
"In Review" | Create task for compliance team, send Slack notification |
"Abandoned" | Send reminder email with a fresh verification link |
Popular Zap Templates
Google Forms → Didit → Gmail
User fills onboarding form → verification session created → result emailed to user and admin.
HubSpot → Didit → HubSpot
New contact → trigger KYC → update contact properties with verification status and ID data.
Stripe → Didit → Slack
New customer → verify identity → notify your team on Slack with the result.
Webhook → Didit → Airtable
Custom trigger → verify user → log session results in Airtable for compliance records.
Available Triggers & Actions
Triggers (start a Zap)
| Trigger | Description |
|---|---|
| Session Status Updated | Fires when any verification session changes status (Approved, Declined, In Review, etc.) |
Actions (do something)
| Action | Description |
|---|---|
| Create Verification Session | Creates a new session with your workflow, callback URL, and vendor data |
| Retrieve Session | Fetches full details and decision data for a given session ID |
Tips & Best Practices
Use Vendor Data to link sessions
Use Vendor Data to link sessions
Always pass a unique identifier (email, user ID, or UUID) in the Vendor Data field when creating sessions. This lets you match verification results back to the correct user in your system.
Handle all status outcomes
Handle all status outcomes
Build Zap paths (using Zapier’s Paths feature) to handle different statuses differently — Approved, Declined, In Review, Resubmitted, Abandoned, and Expired each deserve a tailored response.
Use Filters to reduce noise
Use Filters to reduce noise
Add Zapier Filters to only trigger downstream actions for specific statuses. For example, only send a welcome email when status is
"Approved".Test before going live
Test before going live
Use Zapier’s test feature along with Didit’s Try Webhook button (in Console → API & Webhooks) to validate your Zap end-to-end before processing real users.