Skip to main content
The Zapier integration lets you connect Verilock events to thousands of apps without writing code. Use “Webhooks by Zapier” to catch Verilock events and trigger actions in Google Sheets, Notion, Gmail, Slack, and more.

Prerequisites

  • A Zapier account (Free plan or above)
  • Verilock Business or Enterprise plan

Setup

1

Create a New Zap

Log in to zapier.com and click Create Zap. For the trigger, search for and select Webhooks by Zapier.
2

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.
3

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
Click Save to activate.
4

Test the Trigger

Click Send Test Event in the Verilock dashboard. Return to Zapier and click Test trigger to confirm the payload was received.
5

Add an Action

Choose your destination app (e.g., Google Sheets, Notion, Gmail) and map the Verilock event fields to the action fields.
6

Publish the Zap

Click Publish to activate your Zap. Events will now flow from Verilock to your chosen destination automatically.

Event Payload

Zapier receives the same payload structure as standard Verilock webhooks:
{
  "event": "session.approved",
  "data": {
    "session_id": "ses_a1b2c3d4e5f6",
    "status": "approved",
    "risk_score": 12,
    "applicant": {
      "first_name": "Jean",
      "last_name": "Dupont",
      "email": "jean@example.com"
    },
    "completed_at": "2026-03-15T14:30:00Z"
  },
  "timestamp": "2026-03-15T14:30:01Z",
  "webhook_id": "wh_evt_9f8e7d6c5b4a"
}

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:
EventDescription
session.approvedIdentity verification approved
session.declinedIdentity verification declined
session.completedVerification session finished
aml.match_foundAML watchlist match detected
transaction.flaggedTransaction flagged for review
transaction.blockedTransaction automatically blocked
You can create multiple Zaps with different event subscriptions. For example, one Zap for approved sessions going to Google Sheets and another for AML matches going to email.

Multi-Step Zaps

For complex workflows, chain multiple actions in a single Zap:
  1. Trigger: Verilock session.declined event
  2. Filter: Only continue if risk_score > 70
  3. Action 1: Create a Jira issue for compliance review
  4. Action 2: Send a Slack message to the #compliance channel
  5. Action 3: Add a row to a Google Sheets audit log
Multi-step Zaps require a Zapier paid plan. Free accounts are limited to single-step Zaps.

Troubleshooting

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.
Re-test the trigger in Zapier to refresh the sample data. Zapier uses the test payload to determine available fields for mapping.
Verilock may retry failed deliveries. Use the webhook_id field as a deduplication key in your Zap by adding a filter or lookup step.