Salesforce is a well-known frequently-used CRM among many companies across many industries. journy.io therefore decided to deeply integrate to offer full bi-directional CDP functionalities with enriched SaaS customer intelligence and trigger most important actions for both contacts and accounts, upon getting B2B product-led growth signals.

Your marketeers, sales engagement and customer success teams will be able to start automations, and get tasks on B2B SaaS conditions otherwise simply not possible in native Salesforce.

How to connect Salesforce

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

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

Review the permissions and accept:

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

Salesforce General settings

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

Here are the different settings:

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

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

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

Salesforce source settings

In the source settings you can choose to:

  • Create users in journy.io when a Salesforce contact is created or updated.

  • Create accounts in journy.io when a Salesforce company is created or updated.

  • Link the users and accounts in journy.io based on the relationships you have in Salesforce

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).

Salesforce destination settings


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

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

When no segments are selected, journy.io will sync every user and account to Salesforce. To sync only a subset of users or accounts to Salesforce, 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 Salesforce. You can allow journy.io to create contacts or companies in Salesforce 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 => Salesforce email property

journy.io first_name property => Salesforce firstname property

journy.io last_name property => Salesforce lastname property

journy.io phone property => Salesforce phone property

For companies we'll map the following fields automatically:

journy.io domain identifier => Salesforce domain property

journy.io name property => Salesforce name property

So you'll only need to map the extra properties you want to sync to Salesforce in the settings. You can map any journy.io property to any supported property in Salesforce. 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 Salesforce.

Salesforce logs

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

Salesforce 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 Salesforce actions can be triggered:

  • Create a task: Creates a task in Salesforce for PLG user/account. You can select the Salesforce user the task should be assigned to, next to selecting task type and priority.

Did this answer your question?