Pipedrive Integration

Updated 1 Oct 2026 by Haydn

The Pipedrive integration keeps Journeybee and Pipedrive in step across leads, deals, people, organisations and notes, and adds a Journeybee widget inside Pipedrive so your sales team can create and link partner leads without leaving their CRM.

Where to find it: Go to Settings, then Integrations. Pipedrive sits under the CRM section.

Who can use this: An admin connects and configures the integration. Once it is connected, anyone on your Pipedrive team can authorise and use the widget, with no Journeybee licence needed.

Before you start

You need to be signed in to both Journeybee (as an admin) and Pipedrive in the same browser.
Your Pipedrive user needs permission to manage deals, people, organisations and custom fields, because connecting creates fields, filters and webhooks in your Pipedrive account.
Set up your partner stages, deal stages and custom fields first, because the configuration screen maps against whatever exists at the time. See Stages and Custom Fields.

Connecting Pipedrive

Go to Settings, then Integrations, and open the Pipedrive card.
Select Connect. You are taken to Pipedrive's consent screen.
Select Allow and Install. You are brought back to the Pipedrive configuration page in Journeybee.
Open Configure and set up your mapping. Nothing syncs until you do.

During connection Journeybee sets up everything it needs inside Pipedrive automatically: hidden Journeybee ID fields on organisations, people, leads and deals, a set of Journeybee filters, and secure webhooks. The ID fields are deliberately hidden from Pipedrive's normal field views, because they are how records stay matched, so they should not be deleted.

The connection belongs to your company, not to the person who made it. Team members authorising the widget later never affects it.

The configuration screen

The Pipedrive configuration page has four areas in its sidebar:

Integration: the connection itself, plus Remove Integration if you ever need to disconnect.
Configure: all sync settings, field mappings and stage mappings, grouped into sections.
Import: load records from Pipedrive and bring partners or deals into Journeybee.
Manage: back to all integrations.

Each section shows a status of Not configured, Configured or Changes pending, and mapping sections show how many of their mappings are complete. Use the search box, the Only unmapped filter and Auto-match, which fills in every field that has exactly one matching Pipedrive field, to work through a long list, then save. Changes apply to future sync activity, not retrospectively.

Lead and deal sync settings

One-way creation sync to Pipedrive: new Journeybee leads and deals create Pipedrive records, but later Journeybee edits do not change them. Pipedrive changes still sync back. Notes are not affected.
Show account owner to partners: off by default. When on, partners see a read-only Account owner block on their leads and deals in the partner portal, listing the record owner's name, title, photo and email. The CRM is never named to the partner, and reassigning the owner stays in Journeybee.
Unique field matching: choose a matching field for people, organisations, leads and deals so existing Pipedrive records are recognised instead of duplicated.
Sync on Lead Status: restrict sync to leads with the statuses you tick (New, Accepted, Rejected). Deals follow their lead's status. Leave it empty to sync every status.
Lead note sync direction and Deal note sync direction: set separately, with four options each. Bi-directional sync, Journeybee to Pipedrive only, Pipedrive to Journeybee only, or do not sync notes.

Partner sync settings

Identifying field and value: the Pipedrive organisation field that marks a record as a partner, for example Type = Partner.
Create a new organisation if we don't find one: Yes or No.
Unique partner field and unique partner contact field (Email, First Name or Last Name): pair them with Pipedrive fields to prevent duplicates.
Distributor and reseller link: an organisation-type field used to record distributor-to-reseller relationships. See Distribution Management.

Field and stage mapping

Field mapping is what actually turns sync on. A Pipedrive object is only created or updated if you have mapped at least one field for it.

Partner Organization Fields: partner name, primary domain, website, description, email, phone number, country, stage, category and tier, plus partner custom fields. A change to a mapped partner name, website, description, email, phone number, country, category or tier in Pipedrive also updates the partner in Journeybee, and an empty value leaves the Journeybee value as it is. Primary Domain is sent to Pipedrive but never changed from it, because it controls portal access.
Partner Contact Fields: First Name, Last Name, Email, Phone Number and Position/Title, plus a Partner Organization (Link) field that links the contact to their partner organisation.
People, Organization and Lead fields for Journeybee leads: map lead details on to the Pipedrive records you use. The lead's Company Name maps to the Organisation and the Pipedrive Lead only — it is never written to the Person.
Deal fields: deal name, deal value, commission value, expiration date and deal custom fields.
Partner Stages: choose a Pipedrive organisation field, then map each Journeybee partner stage to one of its values.
Deal Pipeline Stages: map each Journeybee deal stage, per partner type, to a stage in your Pipedrive pipeline, including Won and Lost.
Deal Pipeline Routing: route deals into different Pipedrive pipelines per partner type, based on a custom field value.
Stage changes stay in the deal's pipeline: updating a deal's stage in Journeybee writes the mapped stage in whichever pipeline the deal already lives in — it never moves the deal between pipelines. Only a change to the Deal Pipeline Routing custom field moves a deal, and a deal sitting in a pipeline the integration does not map gets no stage writes at all. If Journeybee cannot read the deal's current stage and pipeline in Pipedrive, it leaves them untouched while the other fields still sync.

What syncs and when

Journeybee to Pipedrive happens within seconds of a change. Rapid edits are batched into a single write.
New Pipedrive deals and note changes arrive in near real time through webhooks.
All other Pipedrive edits, to people, organisations and existing deals, are picked up by a scheduled sync every 15 minutes, so they can take that long to appear.
No echo back to Pipedrive: when a Pipedrive record creates something in Journeybee — through an import, the deal webhook or a scheduled sync — Journeybee does not update that Pipedrive record. The only writes are the hidden Journeybee ID fields and, on a new deal, the link to the partner's organisation, which keep the records linked. Those writes can still trigger Pipedrive automations, so exclude the Journeybee fields from any automation trigger that should not react to an import or sync.

Deals stay linked through the Pipedrive deal ID, and every other record through the hidden Journeybee ID fields, so records match reliably in both directions.

Importing existing Pipedrive data

Partners

Set the identifying field and value in Partner Sync Settings, and choose the partner type for the import. Only one type can be imported at a time.
Open the Import tab and click Load records. Journeybee lists the matching organisations on the Partners tab, 50 per page, with their Pipedrive contacts underneath. Use Search by name to find an organisation, the page controls to move through the list, and Select all on this page to tick a whole page. Your selections stay in place as you page, search and switch tabs.
Click Import in the bar at the bottom — it counts the partners, contacts and deals you picked. Each organisation becomes a Journeybee partner, with its selected contacts added as partner contacts and the Pipedrive IDs stored so future changes stay linked. The page reports the import's progress until it completes.

Imported partners are created as offline partners, so no portal invitation is sent. Invite them from the partner page when you are ready. Organisations with no associated person that has an email address are hidden from the list, and the list notes how many on the current page were hidden: add a person with an email in Pipedrive to import them. See Partner Contacts.

Deals

Map your deal pipeline stages first, so imported deals land in the right stage.
On the Deals tab (Partners to Import Deals For), select the partners whose deals you want. The list is paged and searchable like the partners list, and shows how many unimported deals each one has.
Click Import in the bar at the bottom to run the import. Journeybee creates a lead and deal for each Pipedrive deal, and repairs existing deals that are missing their link fields rather than duplicating them. An import sends no lead or deal notifications — the records simply appear.

The widget appears on Pipedrive deal, person and organisation detail views.

When the record is not yet linked, the widget lets the user connect it to your partner programme:

Search and pick the partner the record belongs to, and optionally attach partner contacts.
Create the record in Journeybee: for reseller partners, Create Reseller Lead; for referral partners, Send Lead or Lead Received. On a deal view, the deal is created in Journeybee along with the lead.

When the record is already linked, the widget shows a Details tab with the partner at a glance (logo, name, partner type, status, stage, category and tier, plus whether the lead was sent to or received from the partner), followed by a Your Team list of the Journeybee users assigned to the lead or deal and a Partner Team list of the partner contacts on it — each shown only when it has someone in it — and a Lead Notes or Deal Notes tab for reading and adding notes that sync with Journeybee.

If the widget has been open for over an hour it can show Session expired, reopen the Journeybee panel. Close and reopen it to carry on.

Pipedrive only shows the Journeybee widget button to users who have personally authorised the app, which is a one-time step for each person on your Pipedrive team. There are two ways to do it, both while signed in to Pipedrive.

From the Pipedrive Marketplace: find Journeybee in the Pipedrive Marketplace, select Install now, then Allow and Install on the consent screen.

Or with a direct link, which is handy to forward to your team. Each person opens the link for your region and selects Allow and Install:

Enable the Journeybee widget (US and EU)

Enable the Journeybee widget (Australia)

Either way, a confirmation appears and closes itself. After refreshing Pipedrive, the Journeybee widget button appears on their deal, person and organisation views.

No Journeybee sign-in, account or licence is needed. Authorising takes one click and does not add a billable user. An admin must have connected the integration first; otherwise the person sees an "Almost there" page asking them to check with their administrator.

Working with Pipedrive from Journeybee

Open in Pipedrive: leads, deals, partners and contacts show a Pipedrive link that takes you straight to the matching record.
Pipedrive owner: a lead or deal shows the owner of its Pipedrive record, and you can search your Pipedrive users and set the owner without leaving Journeybee.
Linked deals: a lead lists the Pipedrive deals on its linked person or organisation and marks the ones already connected, so you can link an existing deal instead of creating a duplicate.

Reconnecting

If the Pipedrive connection expires or is revoked, syncing pauses safely rather than failing repeatedly. When that happens:

Admins receive an email asking them to reconnect.
Admins also see a banner in Journeybee with a Reconnect button, which leads back to the Pipedrive configuration page.

Reconnecting is the same one-click consent as connecting. Only an admin needs to act: your team's widget authorisations are unaffected, and nobody needs to authorise again. Syncing resumes on the next run.

Troubleshooting

Nothing is syncing at all. Check the section you expect to sync actually has field mappings saved. An object with no mapped fields is never created or updated.
A user cannot see the widget button. They most likely have not authorised the app yet. Have them install Journeybee from the Pipedrive Marketplace or send them the authorisation link above, then refresh Pipedrive. Check too that your Pipedrive account allows that user to install Marketplace apps.
A user sees "Almost there" after authorising. The integration is not connected for your company yet. An admin needs to connect Pipedrive first, then the user can authorise again.
A user sees "Access denied". Their Journeybee access is disabled or unavailable, and an admin can review their status under Team Management.
Syncing has stopped. The connection has most likely expired. Check for the reconnect banner or email and reconnect from the configuration page.
Changes from Pipedrive are slow to appear. New deals and notes arrive in near real time, but other Pipedrive edits are collected every 15 minutes, so a short delay is normal.
Duplicate people or organisations are being created. Set the unique matching fields for people, organisations, leads and deals.
Creating a lead in the widget, or creating a deal from the Linked deals list on a lead, shows an error. Journeybee could not read or write the record in Pipedrive, which is usually temporary, such as Pipedrive rate limiting. Wait a few minutes and try again. If it keeps happening, ask an admin to check the connection on the Pipedrive configuration page.
One record is not syncing, or shows no Pipedrive link. If Pipedrive rejects a change, for example because a required field has no value, Journeybee leaves the record unlinked rather than marking it synced. Check the record's mapped fields for missing or invalid values; the next change to the record tries the sync again. If several records are affected, contact support.

Good to know

Authorising the widget is one-time per person and never affects your company connection or other users.
Pipedrive users who authorise appear in Journeybee as non-billable users, so they do not consume a licence.
The hidden Journeybee fields and filters created in Pipedrive are how records stay linked. They are invisible in Pipedrive's normal field views and should not be deleted.
Notes have their own sync direction, independent of the one-way creation sync setting. Pipedrive and Attio are the two CRM integrations where notes can sync both ways.
Removing the integration stops all syncing but leaves your Journeybee records, and your Pipedrive records, exactly as they are.
For the other tools you can connect, see Integrations.