Skip to main content
Ad leads need the extended CRM and activation by Dealpipe. Only admins set up connections.
Every lead your tool sends to Dealpipe becomes an inquiry under CRM → Leads right away. Dealpipe creates the contact or links it to an existing contact by email address. Routing rules, response time alerts and auto-replies run as for any other inquiry.

Create a connection

  1. Open Settings → CRM → Ad leads.
  2. Choose Add connection → Webhook and enter a name, for example “Zapier Meta campaigns”.
  3. Copy the URL and the secret. The secret is shown only once.
The list shows the last lead received and the last error for each connection. From the row menu you can rename the connection, rotate its secret or delete it. After a rotation the old secret stops working at once. Deleting keeps the inquiries already received. Google Ads sends each lead from a lead form straight to Dealpipe, without Zapier or Make.
  1. Open Settings → CRM → Ad leads and choose Add connection → Google lead forms.
  2. Copy the Webhook URL and the Webhook key. The key is shown only once.
  3. Open the lead form in Google Ads. Under Export leads from Google Ads → Other data integration options → Webhook integration (optional), enter the URL and key.
  4. Choose Send test data. Dealpipe creates a test inquiry without a contact; the connection shows the time and name of the last test lead. Then choose Save.
Real leads become inquiries with campaign, form and Google click ID. The same lead is never created twice, even when Google sends it again. After you rotate the key, enter the new key in every lead form. Leads Google could not deliver while the connection was broken must be downloaded from Google Ads as a CSV. The CSV covers the last 30 days.

Pause a connection

In the connection menu, choose Pause. A paused connection rejects every lead with 403 and stores nothing. Resume makes it accept leads again. Google does not resend leads from the pause; download them as a CSV.

Send a lead

Send one POST request per lead with a JSON object to the connection URL. Put the secret in the Authorization header as a bearer token. Dealpipe also accepts the X-Dealpipe-Secret header.

Fields

Empty values ("" or null) count as missing. Numbers in text fields are kept as text. Dealpipe ignores other fields. Source details are stored only for a newly created contact; an existing contact keeps its first source.

Responses

You can safely resend a lead after an error. Because of lead_id, no duplicate inquiry is created.

Example: Zapier

  1. Choose your ad platform as the trigger, for example Facebook Lead Ads → New Lead.
  2. Add the action Webhooks by Zapier → Custom Request.
  3. Set Method to POST and URL to the connection URL.
  4. Enter the JSON under Data and insert the trigger fields, for example:
  5. Under Headers, add Authorization with the value Bearer <SECRET> and Content-Type with the value application/json.
  6. Test the step. The lead appears under CRM → Leads.

Example: Make

  1. Choose your ad platform as the trigger, for example Facebook Lead Ads → Watch Leads.
  2. Add the module HTTP → Make a request.
  3. Set URL to the connection URL and Method to POST.
  4. Under Headers, add Authorization with the value Bearer <SECRET>.
  5. Choose Raw as Body type and JSON (application/json) as Content type.
  6. Enter the JSON under Request content and insert the trigger fields, as in the Zapier example.
  7. Run the scenario once. The lead appears under CRM → Leads.
To test, send "is_test": true. The inquiry appears under CRM → Leads, without a contact, routing or auto-reply.