Connect Pipedrive

Connect your Pipedrive account in minutes – no API keys, no webhooks to wire by hand. Authorize once and three default triggers (Lead Created, Deal Created, Deal Closed-Won) are installed for you, ready to map onto your conversions.

Connecting Pipedrive turns CRM events – new leads, new deals, closed-won deals – into LeadJourney conversions, automatically attributed to the campaign, ad set and ad that earned them. You authorize Pipedrive once (no keys to copy, no webhook URLs to paste by hand), then map each Pipedrive event onto one of your conversion types. Mapped events flow through the same postback pipeline as your offline conversions, so they automatically pick up every ad postback you've already configured.

Before you start

Have these ready so the connection works end to end:

An active LeadJourney workspace and a Pipedrive account you can sign in to.
Tracking is live – clicks have to be recorded first so deals can be matched back to a campaign. See Install the tracking script.
At least one conversion type to map onto (e.g. WonClient). Set these up first in the Events Manager.

Where to find it

Open Settings → Apps, or go to app.leadjourney.io/settings?slug=apps. Click the Pipedrive card to open the integration. While you're not connected you'll see a “Connect your Pipedrive workspace” card; once connected, the same screen shows your company and triggers.

Step by step

Authorize LeadJourney from Pipedrive

On the Connect your Pipedrive workspace card, click Connect with Pipedrive. You'll be redirected to Pipedrive to sign in and approve LeadJourney's access.

The grant gives read access to your leads, deals and contacts, plus webhook management so LeadJourney can subscribe to lead and deal events – there are no keys to copy and no webhook URLs to paste. After you approve, Pipedrive sends you back and you'll see a “Pipedrive connected” confirmation.

Three triggers are set up for you

On connect, LeadJourney installs three default triggers – Lead Created, Deal Created and Deal Closed-Won – so you're not starting from a blank slate. Edit, pause or delete them like any other trigger, and add more whenever you need.

Check the connection details

Once connected, the header shows everything at a glance: a Live pill (or Needs reconnect if something breaks), your connected company, how many triggers are active, and the date you connected. A Disconnect button lives in the same header for later.

Add or edit a trigger

In the Triggers panel – “Each trigger maps a Pipedrive event to one of your conversions.” – click Add trigger (or Edit one of the defaults). In the New Pipedrive trigger dialog:

App – Pipedrive (already selected).
LeadJourney Event – pick the conversion type this Pipedrive event should record, e.g. WonClient. (No options? Create one under Settings → Events first.)
Trigger – choose the Pipedrive event that should fire it: Lead Created, Deal Created or Deal Closed-Won.

Click Continue.

Receive data and confirm the mapping

The dialog opens a three-tab flow:

Receive Data – click Check for Data to pull recent records for the event you picked. If nothing appears, create or win a deal in Pipedrive and check again, then select a record to map against.
Configure Mapping – map the Pipedrive record onto LeadJourney columns – Email, Name, Phone, click_id, Revenue and Currency – using Add custom field for anything extra. Mapping click_id is recommended but optional (see the callout below).
Filtering (optional) – add conditions so the trigger only fires for matching records.

Click Activate to finish.

Why deals link to the right campaign automatically

Pipedrive carries the visitor's click ID in its tracking.salesforce_uuid field, which LeadJourney's landing-page tracking populates – and the trigger auto-maps click_id to it for you. So when a deal is created or won, LeadJourney already knows which click – and therefore which campaign, ad set and ad – earned it. Just make sure your leads enter Pipedrive from LeadJourney-tracked pages so the tracking field is filled in.

Managing your triggers

Each trigger appears as a row – Pipedrive event → conversion type – with an Active / Paused pill and a summary of how many fields and filters it uses.

Pause / Resume – temporarily stop a trigger without deleting it.
Edit – change the mapping, filters or target conversion.
Delete – remove a single trigger; others keep running.
Add another – use Add trigger again to map more Pipedrive events onto different conversions.

Reconnecting

If Pipedrive revokes the app, the webhook subscriptions go missing, or Pipedrive is unreachable, the header flips to Needs reconnect and shows a banner explaining why. Click Reconnect to re-run the authorization – your triggers stay in place.

Disconnecting

To remove Pipedrive, click Disconnect in the header and type disconnect to confirm. This is deliberate because it's destructive:

Disconnect deletes your triggers

Disconnecting permanently removes the Pipedrive connection, deletes every trigger and revokes the webhook subscriptions. Pipedrive events stop flowing into your conversions immediately. You can reconnect later, but your trigger configuration won't be restored – you'll set them up again.

Troubleshooting

No records when you click “Check for Data”?

Nothing recent exists in Pipedrive for that event yet. Create a lead, create a deal, or mark a deal as won, then click Check for Data again. The matching record should appear so you can finish the mapping.

Deals come in but aren't attributed to a campaign?

LeadJourney needs to know which click the deal belongs to. Check that (1) the tracking script is installed and recording clicks, (2) leads enter Pipedrive from LeadJourney-tracked pages (so tracking.salesforce_uuid carries the click ID), and (3) the trigger is Active. As a fallback you can map click_id, email or phone explicitly on the Configure Mapping tab.

Header shows “Needs reconnect”?

Pipedrive has revoked the grant, the webhooks are gone, or the API is unreachable. Click Reconnect in the banner to re-authorize. Your triggers are preserved.