Contents:

• Overview
• Use Cases
• Setting up LeanData-Gong Integration
• Prerequisites
• Authorizing Gong in LeanData
• Gong Add to Flow FlowBuilder Node
• Gong Remove Person from Flow FlowBuilder Node
• Audit Logs

 

Overview

Joint Gong and LeanData users can route a prospect to the right rep with the appropriate context and then immediately queue the prospect for automated engagement, all from the LeanData FlowBuilder interface. After assignment by LeanData you can automatically add prospects to a Gong Flow based on intent signals and keywords for fast and effective outreach. Prospects can also be automatically removed from a Gong Flow directly from a LeanData Action.

Use Cases

• Improve Rep Productivity: Automatically add inbound leads based on campaign source to the right Gong Flow in the right rep's name.
• Automatic Prioritization: Add less engaged leads based on title or persona to the right Gong Flow for any outbound communication. 
• Automated Flow Management: Automatically remove prospects from Gong Flows when they've been disqualified, converted, or no longer meet engagement criteria.

 

Setting up LeanData-Gong Integration

Prerequisites

• Joint Customer of LeanData and Gong Engage.
• Advanced or Premium Package with LeanData Lead and Contact Router

Authorizing Gong in LeanData

• From the LeanData app, navigate to Integrations > Routing tab > Gong and click the Get Started button.

• From the Gong Engage Integration page enter a Flow Owner Email. This email should be for a Gong Flow Owner who has access to company Flows in your Gong Instance. Please note: Only company Flows will be accessible by LeanData.
• Select whether you would like to access Flows from All Workspaces or an Individual Workspace. In the case of an Individual Workspace, please enter the Workspace ID (You can find any workspace ID by going to Gong > Company Settings > Workspaces. Click any workspace and the workspace ID can be found in the webpage URL).

 

• Click Authorize Gong, and log in to your Gong instance to complete the authorization.

For a video walkthrough of the above steps, please see: Gong Authorization.

Gong Add to Flow FlowBuilder Node

Once the above steps have been completed, you can utilize the Gong Add to Flow Node from either Lead or Contact Router.

This node can be found under Integrations > Sales Engagement > Gong in the Node Bar.

Within the Add to Flow Node, there are a few configurable options:

Which Flow do you want to add the prospect to?

In the Which Flow do you want to add the prospect to? section, you need to select the Flow where you want to add the prospect. There are two options available:

Specific Flow

With this option, you will select a specific Flow from a dropdown list of Master Flows synced from Gong.

If you have recently added or updated your Flows and they don't appear in the dropdown, click the circular refresh icon to sync your Flows.

Flow ID from a Variable

The Flow ID from a Variable option lets you dynamically reference a Flow ID stored in a variable. This ID corresponds directly to the Flow's identifier in Gong. The Flow ID must be stored in a variable or field located upstream in your graph. For instance, if you want to match specific Campaigns to particular Flows, you can create these mappings in a Data Table and set a Flow ID variable in this node to add the Lead/Contact to the correct Flow.

Assignee for Flow

You must select an Assignee for the Flow. The Assignee is the rep accountable for running the email, call, or other steps associated with the person in the selected Flow. Flow steps will be assigned to the designated assignee. Automated emails will also come from the assignee selected.

You can select the Lead / Contact Owner, a User Found on a Variable Field like from a matched Account, or you can select a Specific User from a dropdown that will list your Gong Users.

Advanced Settings

There are a number of fallback edges you can select:

• Next Node: This option allows the record to proceed to another node in the Router graph after the record has been added to the Gong Flow. This can include things like sending a notification or updating a field on the record.
• No User in Field: This option will allow you to direct next actions if there is no user in the Variable field selected in the Assignee for Flow section above.
• Configuration Error: This will allow you to direct the next actions in the case of an error.
• Queue Owner: This will allow you to direct the next actions in case the intended assignee is a queue.

Gong Remove Person from Flow FlowBuilder Node

In addition to adding prospects to Gong Flows, you can also remove a person from a Gong Flow using the Gong Remove Person from Flow Node from either Lead or Contact Router.

This node can be found under Integrations > Sales Engagement > Gong in the Node Bar.

Within the Remove Person from Flow Node, there are a few configurable options:

Which Flow do you want to remove the prospect from?

In the Which Flow do you want to remove the prospect from? section, you need to select the Flow you want to remove the prospect from. There are two options available:

Specific Flow

With this option, you will select a specific Flow from a dropdown list of Flows the person is assigned to, synced from Gong.

If you have recently added or updated your Flows and they don't appear in the dropdown, click the circular refresh icon to sync your Flows.

Flow ID from a Variable

The Flow ID from a Variable option lets you dynamically reference a Flow ID stored in a variable. This ID corresponds directly to the Flow's identifier in Gong. The Flow ID must be stored in a variable or field located upstream in your graph. For instance, you populate Flow IDs into a variable based on routing criteria in a Data Table and set a Flow ID variable in this node to remove the Lead/Contact to the apporpriate Flow.

Who should be credited as the person removing the prospect?

You must select a User who will be the user of record for remove the prospect.

You can select the Lead / Contact Owner, a User Found on a Variable Field like from a matched Account, or you can select a Specific User from a dropdown that will list your Gong Users.

Advanced Settings

There are a number of fallback edges you can select:

• Next Node: This option allows the record to proceed to another node in the Router graph after the prospect has been removed to the Gong Flow. This can include things like sending a notification or updating a field on the record.
• No User in Field: This option will allow you to direct next actions if there is no user in the Variable field selected in the Who should be credited as the person removing the prospect? section above.
• Configuration Error: This will allow you to direct the next actions in the case of an error.

 

Monitoring and Troubleshooting

Audit Logs

Gong Add to / Remove from Flow actions are included in LeanData Audit Logs:

 

For more information, please submit a ticket with LeanData support.