Webhook Lead Capture

The Webhook Lead Capture in Driftrock lets you receive leads from any source that is not available as a native integration. If a partner, custom web application, or internal system can send an HTTP POST request, you can connect it to Driftrock in minutes and benefit from the same validation, deduplication, and CRM routing as any other capture type.

What is the Webhook Lead Capture?

The Webhook Lead Capture provides a secure API endpoint and unique key that a partner or developer sends lead data to. Each capture has its own credentials, so you can connect multiple sources independently, track them separately in reporting, and revoke access to a single partner without affecting others.

Once a lead is submitted to the endpoint, Driftrock authenticates it using the key, maps the incoming fields to your standard field schema, runs validation and deduplication, and routes the lead to your CRM according to your configured automations.

A built-in Share Documentation feature generates a live link containing the exact JSON schema, required fields, and acceptable values that your partner needs. This removes the back-and-forth of sharing credentials and technical specs manually.

Why use the Webhook Lead Capture?

Many lead sources — such as custom vehicle configurators, niche automotive portals, or internal databases — do not have a pre-built Driftrock connector. Without a generic webhook, these sources require manual CSV exports or bespoke development to get leads into the CRM. The Webhook Lead Capture removes both of these options in favour of a self-serve setup that takes minutes.

Because the connection runs through the full Driftrock pipeline, every lead from a webhook source benefits from the same quality controls and reporting as any social or search channel.

How it works

An Admin generates a unique API key in Settings, then creates a new Webhook Capture in the Capture Library.

The partner or developer is given the API key, Source ID, and the Share Documentation link.

The partner configures their system to POST lead data to the Driftrock endpoint, including the API key in the header and the correct event type (set to "lead").

Driftrock authenticates the request, maps the fields, and routes the lead through the standard pipeline.

The lead appears in Your Captures and is delivered to your CRM.

Getting started

Prerequisites: Admin access to your Driftrock account to manage API keys. Your partner needs to be able to configure an HTTP POST request.

Go to Settings, then API Settings, and create a new API key named after the partner or source.

In the Capture Library, select Webhook Capture and click Setup.

Choose Lead as the event type and complete the capture build.

Map the fields you expect to receive in the Mapping step.

Click the Share button to generate the documentation link and share it with your partner along with the API key and Source ID.

Ask the partner to send a test lead and verify it arrives correctly in Your Captures.

Complete the Destinations step to map fields to your CRM and activate the capture.

Important: Ensure the lead payload includes

event_type: lead

and the correct source name. Without these, leads will not be processed correctly.

Tips for getting the most out of the Webhook Lead Capture

Create a separate API key for each partner so you can track their leads independently in reporting and revoke access for one source without affecting others. Use the Share Documentation feature to give partners a live link with the exact specifications rather than sending static documents that may become outdated.