Overview
The Gong integration allows Alysio to securely connect with your Gong workspace to retrieve conversation intelligence, call transcripts, and sales engagement workflow data. Once connected, Alysio can query Gong call records, retrieve call transcripts and extended conversation insights, identify Gong users, and interact with Gong Engage flows. Revenue teams can request this information directly through Alysio using natural language, allowing them to quickly analyze conversations and take action without navigating the Gong interface. The integration enables organizations to combine conversation intelligence with CRM data, pipeline activity, and automated workflows within the Alysio platform. Unlike many integrations, Gong authentication is performed once at the organization level. A Gong administrator establishes a single OAuth connection that is shared across the organization. Individual users do not need to authenticate with Gong separately. User-level access to calls and conversations is enforced using Gong permission profiles, ensuring each user only sees data they are authorized to access.Supported Data and Capabilities
The Gong integration enables Alysio to access several key conversation intelligence objects.Users
Retrieve information about Gong users using their user ID. User details can be used when filtering calls or identifying flow owners.Calls
Retrieve lists of calls recorded within Gong. Users can retrieve call details, transcripts, and extended conversation insights including highlights, outlines, and key conversation topics. Call results are filtered based on the user’s Gong permission profile.Call Transcripts
Retrieve transcripts associated with Gong calls. Transcripts allow revenue teams to analyze conversations, extract insights, and review key discussion points.Detailed Call Insights
Retrieve extended call metadata including: Conversation highlightsCall summaries
Conversation outlines
Key discussion points
Participants and engagement metrics
Engage Flows
Retrieve Gong Engage flows used for automated outreach sequences. Users can list flows owned by specific users or identify flows associated with prospects.Prospect Flow Assignment
Assign Engage flows to CRM prospects. This allows teams to trigger outreach sequences directly from Alysio.Authentication
The Gong integration uses OAuth 2.0 authentication. However, Gong authentication is performed at the organization level, not the individual user level. A Gong administrator must authorize the integration once through the Alysio Settings → Integrations panel. Once connected, the integration applies to the entire organization. Users within the organization do not need to authenticate separately.Credential Handling
OAuth tokens are securely stored within Alysio and automatically refreshed when necessary. Because Gong uses an organization-level connection, the same credential is used for all users in the workspace. When requests are made to the Gong API, Alysio includes the requesting user’s Gong user ID to enforce Gong permission rules. If the integration is disconnected by an administrator, Gong functionality will no longer be available until the administrator reconnects the integration.Required Permissions and Scopes
The Gong integration may request access to the following API scopes.| Scope | Purpose |
|---|---|
| api:calls:read:basic | Retrieve call metadata |
| api:calls:read:transcript | Retrieve call transcripts |
| api:calls:read:extensive | Retrieve detailed call insights |
| api:users:read | Retrieve Gong user information |
| api:flows:read | Retrieve Engage flow information |
| api:crm:get-objects | Access CRM-related objects |
| api:workspaces:read | Retrieve workspace information |
| api:stats:interaction | Access interaction statistics |
| api:stats:user-actions | Access user engagement metrics |
| api:stats:user-actions:detailed | Retrieve detailed interaction data |
| api:stats:scorecards | Retrieve coaching scorecards |
| api:permission-profile:read | Enforce Gong permission visibility |
| api:tasks:read | Retrieve task information |
| api:library:read | Access Gong content libraries |
| api:crm-calls:manual-association:read | Retrieve call associations |
| api:call-outcomes:read | Retrieve call outcome data |
MCP Tools
The Gong MCP provides tools that allow Alysio to retrieve conversation intelligence and interact with Gong Engage flows.get_gong_user_details
Retrieves information about a Gong user. Example prompts Get Gong user 123Who is this Gong user
list_gong_calls
Lists calls available to the requesting user. Example prompts List my Gong calls from last weekShow calls I have access to Results are filtered based on the user’s Gong permission profile.
get_gong_call_details
Retrieves detailed metadata for a specific call. Example prompts Show details for call 789Get information about this Gong call
get_gong_call_transcript
Retrieves transcripts for one or more calls. Example prompts Show transcript for call 789Get the transcript for this conversation
get_detailed_gong_call_details
Retrieves extended call insights including highlights, summaries, and conversation outlines. Example prompts Show extended details for this callGet full conversation insights
gong_engage_flows_list
Lists Engage flows owned by a specific user or workspace. Example prompts List my Engage flowsShow flows owned by this user
gong_engage_flows_for_prospects
Lists flows currently assigned to a CRM prospect. Example prompts What flows are assigned to this prospectShow outreach flows for prospect 123
gong_engage_flows_assign_to_prospect
Assigns an Engage flow to one or more CRM prospects. Example prompts Assign this flow to prospect 456Add prospect to flow 123
App Behavior
Alysio retrieves Gong data on demand when users request conversation intelligence insights. There is no background synchronization between systems. Instead, API requests are executed in real time when users query call data, retrieve transcripts, or interact with Engage flows. All API requests are sent using the organization’s OAuth credential while applying the requesting user’s Gong user ID to enforce permission visibility.Example Workflow
User asks What Gong calls did I have last week Alysio routes the request to the Gong MCP. The MCP includes the requesting user’s Gong user ID and date filters. The system sends a request to the Gong API using the stored OAuth credential. The returned calls are filtered according to the user’s Gong permission profile. Alysio displays the filtered call list in the conversation interface.Troubleshooting
Gong Not Connected
The integration has not been authorized by a Gong administrator. SolutionA Gong administrator must connect Gong through Settings → Integrations.
Authentication Error
The OAuth credential may have expired or been revoked. SolutionReconnect the Gong integration through the integrations settings.
Missing Call Data
Call visibility is controlled by Gong permission profiles. SolutionVerify that the user has permission to access the requested calls within Gong.