Skip to main content

Setup Guide: Pipedrive

How to connect Pipedrive to LettrLabs via Zapier and trigger mail from deal data.

A
Written by Adam Rutkowski

Pipedrive has a native Zapier app. If you haven't set up the LettrLabs side of Zapier yet, start with Setup Guide: Zapier first.

Before you start

  • A LettrLabs API key and an Integration Order created for Zapier (Setup Guide: Zapier, Steps 1–2).

  • A Pipedrive account with permission to authorize new app connections.

Step 1: Connect Pipedrive inside Zapier

In Zapier, start a new Zap, search for Pipedrive, and authenticate with your Pipedrive account.

Step 2: Choose your Pipedrive trigger

  • Updated Deal (recommended) — fires on any deal change. Pair it with a Filter by Zapier step to gate on the specific condition you care about (e.g., a pipeline stage). Keeping that logic in Zapier means whoever manages the Zap can see and adjust it without separate Pipedrive filter-editing access.

  • Deal Matching Filter — fires only when a deal matches a saved Pipedrive filter. Reach for this only when a condition is genuinely awkward to express as a Zapier filter step, since a saved Pipedrive filter needs a Pipedrive-side edit to change later.

  • New Person — for lead-capture-style mail.

Step 3: Add a LettrLabs action

  • Add Recipient to Integration Order for customer-facing mail.

  • Mail Recipients Around an Address (Radius Mail) if the deal or person record includes a job/property address distinct from the contact's own address.

Step 4: Test, then go live

Test the Zap, confirm the sample recipient in LettrLabs, publish, then activate the LettrLabs automation.

Want help picking your first Pipedrive trigger? Reach out to our team.

Did this answer your question?