Topics

Overview

Pipedrive is extremely popular among growing SaaS companies, as well as serving lots of other industries. journy.io therefore decided to deeply integrate to offer full bi-directional CDP functionalities with enriched SaaS customer intelligence and trigger most important activities for both people and organisations, upon getting B2B product-led growth signals.

Your sales teams will be able to start automations, and get activities, on B2B SaaS conditions otherwise simply not possible in native Pipedrive.

How to connect Pipedrive

Go to your connections menu and click the 'Connect' button under the Pipedrive logo:

Open

Choose the Pipedrive account that you want to connect, after login :

Open

Review the permissions and accept:

If you've accepted the permissions, you'll see that Pipedrive is now connected, on top of your connections screen:

Pipedrive general settings

If you go to the 'Connections' menu and click on 'Settings' on the Pipedrive panel, you'll see the general 'Connection' Tab

Here are the different settings:

• Source: When set, indicated whether Pipedrive can be used as source.

• Destination: When set, indicated whether Pipedrive can be used as destination.

• Name: Set/Edit a name for the connection.

Pipedrive source settings

In the source settings you can choose to:

• Create users from persons: Create users in journy.io when a Pipedrive person is created or updated.

• Create accounts from organizations: Create accounts in journy.io when a Pipedrive organization is created or updated.

In order to setup syncing for accounts, review the destination settings too. You'll need to tell us in which field we can find your own account IDs (to uniquely identify accounts).

Pipedrive destination settings

cont.

Owner

When journy.io creates a contact or company in Pipedrive, you can choose the Pipedrive user that will be assigned as owner.

Using segments to limit which users and accounts will be created or updated in Pipedrive

When no segments are selected, journy.io will sync every user and account to Pipedrive. To sync only a subset of users or accounts to Pipedrive, you can select one or more segments that will act as a filter.

Creating or updating

By default journy.io will only update records in Pipedrive. You can allow journy.io to create contacts or companies in Pipedrive when they don't exist yet.

For contacts we'll use the email property to match with users in journy.io.

For companies you'll need to tell us in which field we can find your own account IDs (to uniquely identify accounts). An account ID should be a robust, static, unique identifier that you recognize an account by in your own systems. Ideally, the account ID should be a database ID.

Mapping fields

For contacts we'll map the following fields automatically:

• journy.io email identifier => Pipedrive email property

• journy.io first_name property => Pipedrive firstname property

• journy.io last_name property => Pipedrive lastname property

• journy.io phone property => Pipedrive phone property

For companies we'll map the following fields automatically:

• journy.io domain identifier => Pipedrive domain property

• journy.io name property => Pipedrive name property

So you'll only need to map the extra properties you want to sync to Pipedrive in the settings. You can map any journy.io property to any supported property in Pipedrive. We'll do our best to match the types of the properties. All of the scores you created in journy.io, computed properties, stage, health, ... are mappable to Pipedrive.

Pipedrive logs

At any time, you can check the bi-directional sync logs of your Pipedrive↔journy.io connection by selecting the 'log' submenu.

Pipedrive actions

journy.io eventually allows to define product-led growth signals that trigger actions related to the installed connections. For each user/account meeting signal conditions, following Pipedrive actions can be triggered:

• Add an activity: Creates an activity in Pipedrive for PLG user/account. You can select the Pipedrive user the activity should be assigned to, next to setting activity type and priority.