Pipedrive Integration

The Pipedrive integration keeps Journeybee and Pipedrive in sync — leads, deals, contacts (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. Find Pipedrive under the CRM section.

Who can use this: An Admin connects and configures the integration. Once connected, anyone on your Pipedrive team can enable and use the Journeybee widget — no Journeybee licence needed. The integration requires a paid Journeybee plan.

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.
Configure your sync settings and field mapping (see below).

Connecting must be done by a Journeybee Admin, signed in to both Journeybee and Pipedrive. During connection Journeybee automatically sets up everything it needs inside Pipedrive: a small set of hidden "Journeybee" fields used to link records, filters, and secure webhooks. You won't see the hidden fields in Pipedrive's field lists — that is intentional, and they should not be removed.

The connection belongs to your company, not to individual users. Team members enabling the widget later never affects it.

What syncs

The sync covers leads, deals, contacts (people), organisations and notes, in both directions:

Journeybee → Pipedrive: changes sync in near real time. When a lead, deal, partner, contact or note changes in Journeybee, the matching Pipedrive record is created or updated within moments.
Pipedrive → Journeybee: new deals and note changes arrive in near real time. Other edits — to people, organisations and deals — are picked up by a scheduled sync that runs every 15 minutes, so they can take up to 15 minutes to appear in Journeybee.

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

Sync settings and field mapping

After connecting, the configuration page lets you control exactly how data flows. The main settings:

One-way creation sync: new Journeybee leads and deals create Pipedrive records, but later Journeybee edits won't modify Pipedrive. Updates from Pipedrive to Journeybee still flow. Notes are not affected by this setting.
Unique field matching: choose a matching field for people, organisations, leads and deals so existing Pipedrive records are recognised instead of duplicated or overwritten.
Lead statuses that sync: limit syncing to leads with certain statuses — New, Converted or Rejected. Leave empty to sync all. Deals follow their connected lead's status.
Note sync direction: notes have their own direction setting, separately for leads and for deals — bi-directional, one way in either direction, or off.
Field mapping: map Journeybee lead, deal, partner and contact fields — including custom fields — onto Pipedrive person, organisation, lead and deal fields.
Stage mapping: map Journeybee deal stages to your Pipedrive pipeline stages, and partner stages to a Pipedrive organisation field.
Pipeline routing: route deals into different Pipedrive pipelines per partner type, based on a custom field value.
Partner sync: match Journeybee partners to existing Pipedrive organisations and map partner and partner-contact fields.

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 program:

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

When the record is already linked, the widget shows 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 — and a Notes tab for reading and adding notes that sync with Journeybee.

Pipedrive only shows the Journeybee widget button to users who have personally authorised the app — 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 — handy to forward to your team. Each person opens the link for your region and selects Allow and Install:

→ Enable the Journeybee widget (US & 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.

Reconnecting

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

Admins receive an email asking them to reconnect, with a reminder if the connection is still down a week later.
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 automatically once reconnected.

Troubleshooting

They most likely haven't authorised the app yet — have them install Journeybee from the Pipedrive Marketplace or send them the authorisation link from Enable the widget for your team, then refresh Pipedrive.
Check that your Pipedrive company allows the user to use Marketplace apps — some Pipedrive accounts restrict apps to admins.

A user sees "Almost there" after authorising

The integration isn't connected for your company yet. A Journeybee Admin needs to connect Pipedrive first (see Connecting Pipedrive), then the user can authorise again.

A user sees "Access denied"

Their Journeybee access has been disabled. A Journeybee Admin can review their status under team management.

Syncing has stopped

The connection has most likely expired — check for the reconnect banner in Journeybee or the reconnect email, and reconnect from the Pipedrive 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 — a short delay is normal.

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 — they don't consume a licence.
The hidden "Journeybee" fields 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 setting, independent of the one-way creation sync option.
The integration requires a paid Journeybee plan.