- DarkLight
To work with Gong Engage, an Engage seat is required. Custom flow fields need to be set up for Gong to export Engage activity data to your CRM. This can be done automatically with the Gong for Salesforce app. Setting up flow fields allows reps to filter and find people based on field values. Activities done as part of a flow will have additional fields exported. If custom flow fields are not set up, activities will still be exported but without flow context. Updating settings is necessary to export flow fields to your CRM. Flow data visibility on CRM page layouts requires additional steps. Changing flow field values in Salesforce does not sync with Gong.
Note:
Working with Gong Engage requires an Engage seat.
For Gong to export Engage activity data to your CRM, ensure that your custom flow fields are set up. To save you time, this can be done automatically with the Gong for Salesforce app. Setting up flow fields and exporting them to your CRM also allows reps to filter and find people according to these field values, such as whether or not someone is actively in a flow, which flow they're currently in, the type of step they're on, and more.
Whenever an activity, such as a call or a LinkedIn message, is done as a part of a flow, Gong exports the below fields in addition to the activity's standard fields. One-off activities that are not executed as a step in a flow will be exported without the flow fields. You can also learn more about how different types of Engage activities get exported.
Once custom flow fields are set up in your CRM and flow-related activity takes place, you will start seeing flow fields in your CRM.
Note:
If you change the flow field values or the person’s status in Salesforce, the new values are not synced to Gong.
How to set up custom flow fields
If you're using the Gong for Salesforce app, custom flow fields can be created for you automatically. You can also install the Gong for Salesforce app if you haven't yet.
Alternatively, you can set the fields up manually.
To learn more about automatic vs. manual custom flow field setup, see Create Salesforce tasks for calls and emails.
Export data from flow fields to your CRM
Once the fields are set up, you need to update your settings to ensure that the fields will be exported to your CRM. This will allow reps to filter by flow status fields in Engage.
Learn how to export Engage flow data to Salesforce
Learn how to export Engage flow data to HubSpot
You can also see how Engage exports data to your CRM to learn more about how the data is modeled.
What happens if I don't set up custom flow fields in my CRM?
If you aren't using the Gong for Salesforce app and you don't set up custom flow fields manually, the activity itself will still be exported to your CRM, but without custom flow fields. For example, if you make a call as a step in a flow, the call will be exported to your CRM, but without the flow context that the custom flow fields provide.
Making flow data visible on page layouts in your CRM
Having these flow fields in your CRM database does not automatically expose the fields in page layouts in your CRM. See the following articles to learn about making flow data visible on page layouts in your CRM:
Salesforce: Create Account Page Layouts
HubSpot: Customize the properties in the left sidebar of records
Custom flow fields: Salesforce
Flow data | Adds any Engage data to your tasks and contacts so that you can see which actions were done as part of a flow. By exporting Gong’s Engage data to Salesforce, you can also run Sales-engagement analysis directly in your CRM. | |||
---|---|---|---|---|
Field label name | Description | Object to add field to | Field API Name | Data type |
Engage Flow ID | The ID of the flow the task is associated with. Empty when not associated with a flow. | Task | Gong_Current_Flow_ID__c | Text (30) |
Engage Step Attempt ID | The ID of the action that represents the step in the flow the task is associated with. For example, if a rep makes a phone call as part of a step in a flow, and they had to call 5 times before the person answered, this ID represents one of the times the rep tried to call. | Task | Gong_Flow_Execution_ID__c | Text (50) |
Engage Flow Name | The name of the flow the task is associated with | Task | Gong_Current_Flow_Name__c | Text (100) |
Engage Step Number | The step number in the flow the task is associated with | Task | Gong_Current_Flow_Step_Number__c | Text (10) |
Engage Flow ID | The ID of the flow the contact is in. Empty when not associated with a flow | Contact and lead | Gong_Current_Flow_ID__c | Text (30) |
Engage Step Attempt ID | The ID of the action that represents the step in the flow the task is associated with. For example, if a rep makes a phone call as part of a step in a flow, and they had to call 5 times before the person answered, this ID represents one of the times the rep tried to call. | Contact and lead | Gong_Flow_Execution_ID__c | Text (50) |
Engage Flow Name | The name of the flow the contact is in | Contact and lead | Gong_Current_Flow_Name__c | Text (100) |
Engage Flow Status | The status of the flow the contact is in | Contact and lead | Gong_Current_Flow_Status__c | Picklist. Options are:
|
Engage Step Number | The step in the flow the contact is in | Contact and lead | Gong_Current_Flow_Step_Number__c | Text (10) |
Engage Step Type | The type of step the contact is in | Contact and lead | Gong_Current_Flow_Step_Type__c | Text (80) |
Engage Step Completion Date | The date the current task is due to be completed. For example, if the step is to make a phone call, this field shows the date the call should be made. | Contact and lead | Gong_Current_Flow_Task_Due_Date__c | Date |
Added to Engage Flow By | The name of the Gong user who assigned the contact or lead to a flow | Contact and lead | Gong_Current_Flow_User_Name__c | Text (80) |
Currently in Engage Flow | Indicates whether the contact or lead is currently in an Engage flow | Contact and lead | Gong_Actively_Being_in_a_Flow__c | Checkbox |
Custom flow fields: HubSpot
Flow data | Adds any Engage data to your tasks and contacts so that you can see which actions were done as part of a flow. By exporting Gong’s Engage data to HubSpot, you can also run Sales-engagement analysis directly in your CRM. | |||
---|---|---|---|---|
Field label name | Description | Object to add field to | Field API Name | Data type |
Gong flow ID | The ID of the flow the contact is in. Empty when not associated with a flow | Contact | gong_current_flow_id__c | Text (30) |
Gong step attempt ID | The ID of the action that represents the step in the flow the task is associated with. For example, if a rep makes a phone call as part of a step in a flow, and they had to call 5 times before the person answered, this ID represents one of the times the rep tried to call. | Contact | gong_flow_execution_id__c | Text (50) |
Gong flow name | The name of the flow the contact is in | Contact | gong_current_flow_name__c | Text (100) |
Gong flow status | The status of the flow the contact is in | Contact | gong_current_flow_status__c | Picklist. Options are:
|
Gong step number | The step in the flow the contact is in | Contact | gong_current_flow_step_number__c | Text (10) |
Gong step type | The type of step the contact is in | Contact | gong_current_flow_step_type__c | Text (80) |
Gong step due date | The date the current task is due to be completed. For example, if the step is to make a phone call, this field shows the date the call should be made. | Contact | gong_current_flow_task_due_date__c | Date |
Gong added to flow by | The name of the Gong user who assigned the contact or lead to a flow | Contact | gong_current_flow_user_name__c | Text (80) |
Gong currently in a flow | Indicates whether the contact or lead is currently in an Engage flow | Contact | gong_actively_being_in_a_flow__c | Checkbox |
Possible values for "Engage Flow Status" field
Learn more about flow statuses in your CRM.
Current Values | Description | New values (coming soon) | Description |
---|---|---|---|
Active | The contact/lead is currently active in the flow | In progress | The contact/lead is currently active in the flow |
Paused | The contact/lead is in a flow that was paused, either manually or automatically | Paused | The contact/lead is in a flow that was paused, either manually or automatically |
Opted out | The contact/lead was removed from the flow automatically because they were marked as 'Opted Out' | Opted out | The contact/lead was removed from the flow automatically because they were marked as 'Opted Out' |
Removed Response | The contact/lead was removed from the flow because an email reply was received | Finished (replied) | The contact/lead was removed from the flow automatically because an email reply was received |
Removed | The contact/lead was removed from the flow (not because they were marked as 'Opted Out') | Finished (removed manually) | The contact/lead was removed from the flow (not because they were marked as 'Opted Out') |
|
| Finished (meeting booked) | The contact/lead was removed from a flow |
|
| Finished (no reply) | The contact/lead completed the last step of the flow and did not reply |
|
| Bounced | The contact/lead was removed from the flow automatically because an email bounced |
|
| To-do expired | The contact/lead was removed from the flow automatically because their flow was paused for 30 days |
|
| No license | The contact/lead was removed from the flow automatically because the rep assigned to the flow step does not have an Engage license |
|
| Person deleted | The contact/lead was removed from your CRM |
|
| Flow deleted | The flow was deleted in Gong |