Didit Zapier Integration

Didit is now integrated with Zapier, allowing you to automate identity verification workflows seamlessly. With just a few steps, you can create verification sessions, retrieve session details, and handle updates efficiently.

Key Features

1. Create Verification Sessions

• Initiate verification sessions directly from Zapier.
• Customize sessions with callback URLs, feature settings, and user-specific data.

2. Retrieve Session Details

• Fetch real-time information about a verification session, including user data and session status.

3. Webhook Notifications

• Automatically receive updates on status changes for all verification sessions in your application.

How It Works

Step 1: Authenticate Didit in Zapier

• Use your CLIENT_ID and CLIENT_SECRET from your Didit application to set up the Zapier integration.

Step 2: Create a Verification Session

• Add a Zap trigger (e.g., form submission from Google Forms).
• Use the "Create Verification Session" action in Didit to:
  • Provide a Callback URL for session updates.
  • Define any necessary Features for the session.
  • Include a unique Vendor Data field, such as a user’s email or UUID.
• Share the session URL with the user via email or other communication methods.

Step 3: Set Up Webhook Notifications

• Create a Zap with a webhook trigger using your HubSpot Hook URL.
• Obtain your HubSpot Hook URL from your HubSpot configuration.
• Configure Didit to send status updates to this HubSpot hook by navigating to Verification -> Settings in the Didit app and inputting the HubSpot Hook URL.
• When triggered, use the "Retrieve Verification Session Information" action to fetch session data.

Step 4: Handle Status Updates

• Depending on the session status (e.g., approved, rejected), automate further actions:
  • Update your user database.
  • Modify CRM properties (e.g., in HubSpot).
  • Trigger custom workflows.

Example Workflows

Workflow 1: User Verification via Email

1. A user fills out a form in Google Forms.
2. A new verification session is created in Didit, and the session link is sent to the user via email.
3. The user completes the verification process by accessing the session link.

Workflow 2: CRM Update on Verification Approval

1. The HubSpot Hook URL receives status updates for verification sessions.
2. Zapier retrieves session details using the "Retrieve Verification Session Information" action.
3. If the session is approved, the user is marked as verified in the CRM (e.g., HubSpot).

Best Practices

1. Security:

   • Ensure your CLIENT_ID and CLIENT_SECRET are kept confidential.
   • Treat session URLs as sensitive information.

2. Webhook Configuration:

   • Use the HubSpot Hook URL to maintain consistency and integration within your CRM.

3. Session Monitoring:

   • Regularly review session statuses and logs to address any issues promptly.

4. Communication:

   • Clearly inform users about the verification process and its steps to avoid confusion.

Troubleshooting

• Authentication Issues: Double-check your CLIENT_ID and CLIENT_SECRET.
• Missing Webhook Notifications: Ensure your HubSpot Hook URL is correctly configured in the Didit app.
• Expired Session Links: Recreate the verification session and provide the new link to the user.