Skip to main content

Pipedrive: Native Webhook Setup (No Zapier Required)

Trigger LettrLabs mail directly from a Pipedrive webhook — no Zapier account needed.

A
Written by Adam Rutkowski

Pipedrive has two separate native webhook mechanisms, both independent of Zapier. This guide covers the simpler of the two; see the note at the end for when the more advanced option is worth using instead.

Before you start

  • A LettrLabs Open API key and an inbound webhook connection (see Setup Guide: Open API & Webhooks).

  • A Pipedrive account with access to Tools and Integrations.

Step 1: Create your LettrLabs webhook connection

  1. In LettrLabs, go to Automations > Open API to generate an Open API key.

  2. Go to Active Webhooks > Data Streams (Inbound) > Create, name the connection (e.g., "Pipedrive"), and copy the Webhook URL.

  3. Turn on OpenAPI Key authentication — Pipedrive's classic webhook screen supports HTTP Basic Auth rather than a custom header, so if you need the X-API-KEY header specifically, use the Automations-based webhook (see the note below) instead of the classic screen.

Step 2: Create the webhook in Pipedrive

  1. In Pipedrive, go to Tools and integrations > Webhooks and click Create new webhook.

  2. For Event action, choose the change you want to trigger on (e.g., updated).

  3. For Event object, choose the record type (e.g., deal).

  4. Set the Endpoint URL to your LettrLabs Webhook URL.

Step 3: Test and confirm receipt

Trigger the event in Pipedrive (update a test deal) and check the History tab on your LettrLabs webhook connection.

Step 4: Wire the connection to a mailing and map fields

Open the Automation (Integration Order) or Radius Mail setup, select the Pipedrive connection, choose the action, and map fields — Pipedrive's classic webhook sends the entire record, so there's nothing to configure on Pipedrive's side; all mapping happens here.

Step 5: Go live

Save the webhook connection with a name and confirm the Pipedrive webhook is active.

When to use the newer Automations webhook instead

If you need conditional logic (only fire for deals above a certain value, or in a specific pipeline) that you'd rather build in Pipedrive than in LettrLabs' Inbound Filters, use Tools and integrations > Webhooks > + Webhooks > Automation webhook instead — it supports header-based auth (a better fit for X-API-KEY) and a custom request body, at the cost of being restricted to global admin users.

Want help setting up Pipedrive's native webhook? Reach out to our team.

Did this answer your question?