Overview

HubSpot is about the most popular MAP-CRM-Ticketting all-in-one tool for SaaS companies. 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 companies, upon getting B2B product-led growth signals.

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

How to connect HubSpot

Go to your connections and click the Connect button under the HubSpot logo:

Choose the HubSpot account that you want to connect:

Review the permissions and accept:

If you've accepted the permissions, you'll see that HubSpot is connected:

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

HubSpot source settings

In the source settings you can choose to:

- Create users in journy.io when a HubSpot contact is created or updated

- Create accounts in journy.io when a HubSpot company is created or updated

- Link the users and accounts in journy.io based on the relationships you have in HubSpot

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

HubSpot destination settings

Owner

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

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

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

journy.io first_name property => HubSpot firstname property

journy.io last_name property => HubSpot lastname property

journy.io phone property => HubSpot phone property

For companies we'll map the following fields automatically:

journy.io domain identifier => HubSpot domain property

journy.io name property => HubSpot name property

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

HubSpot logs

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

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

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

  • Add to list: Adds a user to a static list, typically to initiate a workflow such as sending emails.

  • Remove from list: Removes a user from a static list, typically to eject from a workflow such as email drip campaign.

Did this answer your question?