Skip to main content
Connect Didit to 6,000+ apps through Zapier — no code required. Automatically create verification sessions, react to status changes, and sync results with your CRM, database, or communication tools.

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

RequirementWhere to get it
Didit accountSign up at business.didit.me — Free KYC plan is enough to test.
API KeyConsole → API & Webhooks → copy the production key. The Zapier app authenticates with this key for every action.
Workflow IDConsole → Workflows → pick the workflow you want to launch (or create one).
Zapier accountFree or paid — zapier.com. The free plan handles 100 tasks / month, enough for small pilots.

​
How It Works

Connect Didit to Zapier

In Zapier, search for Didit in the app directory (or open the marketplace listing directly) and connect your account using the API Key from Console → API & Webhooks.
Your API Key authenticates all Didit actions in Zapier. You only need to connect once — all your Zaps share the same connection, and rotating the key in Console invalidates the Zapier connection until you reconnect.

Set Up a Trigger

Choose what starts your Zap. This can be a Didit trigger or any other app:
Trigger SourceExample
Didit webhookSession status changes to “Approved”
Google FormsNew form submission → create a verification session
HubSpotNew contact created → trigger KYC
StripeNew customer → verify identity before payout
TypeformOnboarding form completed → start verification

Add a Didit Action

Use one of the available Didit actions (names match the Zapier marketplace listing):Create Verification Session — wraps POST /v3/session/
  • Provide the Workflow ID of the verification flow to execute.
  • Optionally set a Callback URL for the post-verification redirect.
  • Pass Vendor Data (e.g. user email or your internal ID) to link the session back to your records.
  • The action returns the new session_id, the user-facing url, and the initial status — use the url to send the user to the verification flow.
Retrieve Verification Session — wraps GET /v3/session/{sessionId}/decision/
  • Pass a session_id to fetch the full verification result.
  • Access ID data, liveness scores, AML results, the final status, and any uploaded media URLs.

React to Results

Add downstream actions based on the verification outcome:
StatusSuggested 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
Creating a Didit identity verification session from a Zapier action step

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

The names below match the current Didit Zapier app on the marketplace. If you ever see a label that differs slightly inside Zapier itself, trust the Zapier UI — the underlying behavior is the same.

​
Triggers (start a Zap)

TriggerUnderlying eventDescription
Session Status Updatedstatus.updated webhookFires every time a verification session changes status (Approved, Declined, In Review, Resubmitted, Abandoned, Kyc Expired, etc.).

​
Actions (do something)

ActionUnderlying endpointDescription
Create Verification SessionPOST /v3/session/Starts a new session with your workflow, optional callback URL, and vendor_data. Returns the session URL to share with the user.
Retrieve Verification SessionGET /v3/session/{sessionId}/decision/Fetches the full decision payload — ID data, liveness, AML hits, and final status — for a given session_id.

​
Things to know

The Didit Zapier app is intentionally scoped to the highest-value automation surface: launching sessions and reacting to status updates. The following are not currently exposed through Zapier and require a direct API call:
  • Uploading a document image, video, or POA asset from a Zap step.
  • Decision overrides via PATCH /v3/session/{sessionId}/update-status/.
  • KYB-specific endpoints (registries, key people).
  • Webhook event types other than session-level status changes (e.g. transaction.status.updated, user.status.updated).
If you need any of these from a no-code tool, drop into the Sessions API via a Zapier Webhooks by Zapier step with your API Key.

​
Tips & Best Practices

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.
Add Zapier Filters to only trigger downstream actions for specific statuses. For example, only send a welcome email when status is "Approved".
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.

​
Next Steps

Quick Start Guide

Set up your Didit account, create a workflow, and get your API key.

Webhooks

Learn about webhook payloads and signature verification for server-side integrations.