Prerequisites
- A Zapier account (Free plan or above)
- Verilock Business or Enterprise plan
Setup
Create a New Zap
Log in to zapier.com and click Create Zap. For the trigger, search for and select Webhooks by Zapier.
Choose Catch Hook
Select Catch Hook as the trigger event. This creates a unique webhook URL that Zapier will listen on. Click Continue and copy the webhook URL.
Configure in Verilock
Go to Dashboard > Settings > Integrations > Zapier and enter:
- Webhook URL: Paste the Zapier webhook URL
- Events: Select which events to forward to Zapier
Test the Trigger
Click Send Test Event in the Verilock dashboard. Return to Zapier and click Test trigger to confirm the payload was received.
Add an Action
Choose your destination app (e.g., Google Sheets, Notion, Gmail) and map the Verilock event fields to the action fields.
Event Payload
Zapier receives the same payload structure as standard Verilock webhooks:Example Use Cases
Google Sheets Log
Append a new row to a spreadsheet for every completed verification. Track session IDs, applicant names, decisions, and timestamps.
Notion Database
Create a Notion database entry for each AML match, with properties for risk score, match type, and review status.
Gmail Alert
Send an email to your compliance officer when a transaction is blocked, including the full event details.
HubSpot Contact
Create or update a HubSpot contact when a KYC session is approved, syncing verified identity data.
Event Subscriptions
Choose which events are forwarded to Zapier:| Event | Description |
|---|---|
session.approved | Identity verification approved |
session.declined | Identity verification declined |
session.completed | Verification session finished |
aml.match_found | AML watchlist match detected |
transaction.flagged | Transaction flagged for review |
transaction.blocked | Transaction automatically blocked |
Multi-Step Zaps
For complex workflows, chain multiple actions in a single Zap:- Trigger: Verilock
session.declinedevent - Filter: Only continue if
risk_score > 70 - Action 1: Create a Jira issue for compliance review
- Action 2: Send a Slack message to the
#compliancechannel - Action 3: Add a row to a Google Sheets audit log
Troubleshooting
Zap not triggering
Zap not triggering
Verify the webhook URL in Verilock matches the one shown in Zapier. Check that the Zap is published (not in draft mode). Review the Zapier Task History for errors.
Fields not mapping correctly
Fields not mapping correctly
Re-test the trigger in Zapier to refresh the sample data. Zapier uses the test payload to determine available fields for mapping.
Duplicate events
Duplicate events
Verilock may retry failed deliveries. Use the
webhook_id field as a deduplication key in your Zap by adding a filter or lookup step.
