Close is a CRM customer data and engagement tool, extremely popular among 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 leads, upon getting B2B product-led growth (PLG) signals.

Your sales engagement teams will see their sequences automatically be started and paused on PLG contacts — while also automatically getting tasks and opportunities for PLG leads — on B2B SaaS conditions otherwise simply not possible in native Close.

How to connect Close

First, you'll need to create an API key in Close:

We recommend that you name your API key "journy.io" (make sure to copy it!)

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

Paste in the API key you've just generated:

If your API key is valid, you'll see that Close is connected:

Close source settings

In the source settings you can choose to:

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

- Create accounts in journy.io when a Close lead is created or updated

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

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

Close destination settings

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

When no segments are selected, journy.io will sync every user and account to Close. To sync only a subset of users or accounts to Close, 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 Close. You can allow journy.io to create leads in Close when they don't exist yet. Contacts cannot be created by journy.io, as they need to be linked to a lead.

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

For leads 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 => Close email addresses

journy.io first_name property => Close name

journy.io last_name property => Close name

journy.io full_name property => Close name

journy.io phone property => Close phone

For leads we'll map the following fields automatically:

journy.io name property => Close name

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

Close actions

You can trigger the following Close actions using a signal:

  • Create opportunity: Create an opportunity for a lead in Close, thereby selecting the opportunity's status.

  • Create task: Create a task for a lead in Close, thereby selecting assigned user and due date.

  • Enroll in sequence: Add a contact to a Close sequence, thereby selecting the Close email account to send from, as well as assigned users to carry out the sequence tasks.

  • Pause sequence: Pause a contact in a Close sequence.

Note: When creating an opportunity or creating a task, we'll always create a lead regardless whether creating leads is allowed in the connection settings.

Did this answer your question?