Connect a Custom Webhook to Lensmor

Connect your own HTTP endpoint and export selected or filtered Lensmor contacts to it.

Written By Alex Mercer

Last updated 5 days ago

Last updated: September 24, 2026

Use the Webhook integration to send selected or filtered Lensmor contacts to your own HTTP endpoint. Lensmor sends contacts when you start an export from an event; connecting an endpoint does not start a continuous sync.

Before you start

  • Your Lensmor plan must include export access. A Workspace owner or admin manages connections in Integrations.

  • Prepare an endpoint that accepts HTTP POST requests with a JSON body and can parse the Lensmor contact data it receives.

  • Review who can access the receiving workflow or endpoint and where it sends contact data. Hidden contact details remain hidden unless revealed in Lensmor before export.

Connect the endpoint

  1. Copy the URL of your receiving endpoint.

  2. Check that it accepts POST requests with a JSON body.

  3. In Lensmor, open Integrations, find Webhook, and click Connect.

  4. Paste the receiving URL into Webhook URL and click Connect.

  5. Check that the Webhook card shows Connected. Lensmor displays a secret token after connection; keep it secure.

The URL must begin with http:// or https://. Use the general Webhook card for a custom endpoint; the Pipedream, n8n, Make, and Zapier cards validate URLs against those providers.

Export contacts

  1. Open an event and go to Attendees.

  2. Select contacts or apply filters, then open Export and choose Webhook.

  3. Choose Selected Items if you selected contacts, or All Filtered Data for the current filtered result.

  4. Review the count and click Export.

  5. Check your endpoint’s request logs and downstream processing before relying on the result.

Access, Credits, and limits

  • Export requires a plan with export access. Ask a Workspace owner or admin if you cannot manage Integrations.

  • Connecting or exporting does not reveal hidden emails or phones. Revealing contact data is a separate action with its own Credit confirmation in Lensmor.

  • Exports over 50 contacts are sent in multiple batches. A successful Lensmor export does not confirm that downstream processing succeeded.

  • If the receiving URL changes, disconnect and reconnect Webhook with the new URL.