Integrations
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 (or use ?slug=apps&app=pipedrive). 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.
Syncing starts when you connect
LeadJourney tracks new Pipedrive events from the moment you connect. Data from before the connection is not imported.
Check the connection details
Once connected, the header shows a Live pill (or Needs reconnect if something breaks), plus Re-authorize and Disconnect buttons. Below it you'll see the Connection status, your Company with its ID, Active triggers (active out of total) and the Connected since date.
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 from the card grid, e.g. Lead Created, Deal Created or Deal Closed-Won. Search triggers… narrows the list.
- Web Form (web form triggers only): pick the form the trigger belongs to. Pipedrive has no forms API, so the list is built from forms that were submitted recently; a form without a recent submission won't appear yet.
- Attribute changed (optional, on deal update triggers): pick a field and a Target value so the trigger only fires when that field changes to the value. Status, stage and other option fields show a dropdown; leave Any value (or the field blank) to fire on any update.
Click Continue.
Receive data and confirm the mapping
The dialog opens a three-tab flow:
- Receive Data: click Find latest data to pull recent records for the event you picked. If nothing appears, create a lead or deal, mark a deal as won or submit the web form in Pipedrive and check again. Select a record and click Continue with selected record, or Save & return when data is ready to finish later.
- Configure Mapping: map the Pipedrive record onto LeadJourney columns. New triggers start
with Email, Name, Phone, click_id, Revenue and Currency, pre-filled
where LeadJourney finds a likely path. Select several paths to join them with a space, or
type a path or
static:literal and press Enter. Paths that belong to your own team (the deal owner or creator) are marked your team and are never picked automatically. Add custom field brings back a removed column or adds one of your workspace's custom fields, and Create new field creates one (type Text, Number or Currency). Mappingclick_idis recommended but optional (see the callout below). - Filtering (optional): click Add Another Filter and set a path, an operator and a value. Each filter is tested against the record you selected and shows PASS or FAIL, with a summary like “Your trigger would have fired”.
Save & Continue takes you from the mapping to the filters. Click Activate to finish (Save trigger when editing), or Save and continue later to keep your progress.
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. Web form triggers also show the form name.
- Pause / Resume: use the toggle to stop a trigger temporarily without deleting it.
- Edit: change the event, condition, mapping, filters or target conversion. The URL gets a
trigger_idparameter, so you can share a link that opens that trigger directly. - Delete: type
deleteand click Delete trigger. The mapping and filters can't be recovered; other triggers 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 a banner explains why (e.g. “Pipedrive disconnected your app” or “Webhook subscriptions are gone”). Click Reconnect to re-run the authorization. To refresh granted permissions while everything still works, use Re-authorize in the header. In both cases your triggers and settings are kept.
Disconnecting
To remove Pipedrive, click Disconnect in the header, type disconnect and confirm with
Disconnect Pipedrive. 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 “Find latest data”?
Nothing recent exists in Pipedrive for that event yet. Create a lead, create a deal, mark a deal as won or submit the web form, then click Find latest data again. The matching record should appear so you can finish the mapping.
Your web form isn't in the list?
The Web Form list only shows forms with a recent submission. Submit the form once in Pipedrive, then open the trigger again.
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.
Related articles
Attribute Pipedrive web forms
Carry the click ID through a web form so submissions are attributed.
Apps overview
How the Apps page works and what else you can connect.
Events & the Events Manager
Define the conversion types your Pipedrive triggers map onto.
Install the tracking script
Record the clicks that Pipedrive deals get matched back to.
Connect Microsoft Dynamics 365
Connect your Dynamics 365 environment with one authorization, no API keys to copy. All fifteen triggers explained – leads, contacts, opportunities, quotes, orders and cases – plus how to map Dataverse fields so every deal is attributed to the campaign, ad set and ad that earned it.
Attribute Pipedrive web forms
Carry the LeadJourney click ID through a Pipedrive web form so every submission is attributed to the exact campaign – the hidden lj_click_id field, the embed that silently drops it, and the trigger mapping on the LeadJourney side.