Overview
The Gong integration lets users connect their Gong workspace so Alysio can query call data, transcripts, and Engage flows on their behalf. Users can ask Alysio to list calls, get call details or transcripts, look up user details, list Engage flows, see flows assigned to prospects, and assign flows to prospects—all in natural language. The integration uses a single organization-level Gong connection (see Authentication); each Alysio user’s access to calls is then filtered according to Gong permission profiles (e.g. own calls, manager’s team, or reports).
Supported capabilities / objects
- Users — Get details for a specific Gong user (by user ID).
- Calls — List calls (with optional date range and workspace); get call details; get call transcript; get detailed call content (extended context, brief, outline, highlights, etc.). Results are filtered by the requesting user’s Gong permission profile.
- Engage flows — List flows (by flow owner email or user ID); list flows assigned to CRM prospects; assign an Engage flow to prospects.
Authentication
Method: OAuth 2.0 (Gong). The MCP sends requests to the Gong API (https://api.gong.io or the customer-specific base URL) using a Bearer token and credential ID. Gong uses organization-level (global) authentication, not per-user OAuth.
Admin-only connection; no per-user OAuth
Gong does not support user-level OAuth. Authentication is done once at the organization level. A Gong administrator (technical administrator with API access) must connect Gong to Alysio first by completing the OAuth flow in Settings → Integrations. Once that single connection is established, it applies to the entire Gong workspace. Other Alysio users in the same organization do not need to sign in to Gong or complete OAuth themselves—they use Gong through this shared connection. Data access is then governed by Gong’s permission profiles (e.g. which calls each user can see: own, manager’s team, reports, or all), which Alysio enforces using the current user’s Gong user ID when calling the API.
Redirect URI: Configured when the Gong integration is set up in Alysio. The redirect URI must also be registered in the Gong Admin Center (Admin center → Settings → Ecosystem → API) for the OAuth app. Gong’s authorize URL is of the form https://app.gong.io/oauth2/authorize?....
Token handling
- OAuth tokens for the single Gong connection are stored securely and refreshed as needed.
- The same credential is used for all users in the organization; the MCP receives the current Alysio user’s Gong user ID in the request context and uses it to filter call data according to Gong permission profiles.
- If the admin disconnects Gong, the connection is removed and Gong tools are no longer available until a Gong admin reconnects.
Required scopes
api:calls:read:transcriptapi:workspaces:readapi:crm:get-objectsapi:calls:read:extensiveapi:stats:scorecardsapi:stats:interactionapi:stats:user-actionsapi:calls:read:basicapi:tasks:readapi:crm:integrations:readapi:library:readapi:users:readapi:stats:user-actions:detailedapi:permission-profile:readapi:flows:readapi:crm-calls:manual-association:readapi:call-outcomes:read
Admin-only setup: Only a Gong administrator (tech admin) can complete the initial OAuth connection. Ensure your Gong admin connects Gong in Alysio first; other users will then have access without signing in to Gong.
Rate limits and permissions: Gong API rate limits apply (e.g. 3 requests per second, 10,000 per day per Gong docs). Call visibility is limited by each user’s Gong permission profile (own, managers-team, report-to-them, or all).
The Gong MCP exposes the following tools. Users can invoke these capabilities through natural language in Alysio.
| Tool | Description | Example user prompts |
|---|
get_gong_user_details | Returns details for a specific Gong user by user ID. | ”Get Gong user 123”, “Who is user 456 in Gong?” |
list_gong_calls | Lists calls with optional date range and workspace; results filtered by user’s Gong permission profile. | ”List my calls from last week”, “What Gong calls do I have access to?” |
get_gong_call_details | Returns details for a single call by call ID; access checked against user’s permission profile. | ”Show me call 789”, “Get details for this Gong call.” |
get_gong_call_transcript | Returns transcript(s) for specified call ID(s); results filtered by permission profile. | ”Get transcript for call 789”, “Show me the transcript of this call.” |
get_detailed_gong_call_details | Returns extended call content (parties, brief, outline, highlights, key points, etc.) for given call ID(s); filtered by permission profile. | ”Get full details for these calls”, “Show extended content for call 789.” |
gong_engage_flows_list | Lists Engage flows for a user (by flow owner email or workspace); supports pagination. | ”List my Engage flows”, “What flows does this user own?” |
gong_engage_flows_for_prospects | Returns Engage flows assigned to specified CRM prospect ID(s). | ”What flows are assigned to this prospect?”, “List flows for prospect 123.” |
gong_engage_flows_assign_to_prospect | Assigns an Engage flow to one or more CRM prospects (flow ID, prospect ID(s), flow instance owner email). | ”Assign this flow to prospect 456”, “Add prospect 789 to flow 123.” |
App Behavior
- API calls are made on-demand only when the user asks something that requires Gong data (e.g. list calls, get transcript, get user details, list or assign Engage flows). There is no background sync; each request uses the organization’s Gong connection and applies the current user’s Gong user ID for permission filtering.
Example flow
- User asks: “What were my Gong calls last week?”
- Alysio routes the request to the Gong MCP with the user’s Gong user ID in context.
- The MCP builds permission checks (workspace, hierarchy, permission profile), then calls
list_gong_calls with the appropriate date range.
- The request is sent to the Gong API using the stored OAuth credential; the MCP filters the returned calls by the user’s permission level (e.g. own, managers-team, report-to-them).
- The MCP returns the filtered call list; Alysio presents the answer in chat.
Troubleshooting
Common issues
- Gong not connected — No one has completed the Gong OAuth flow. Fix: A Gong administrator must connect Gong in Settings → Integrations (one-time, org-level). After that, other users do not need to sign in to Gong.
- 401 Unauthorized — Token expired or invalid. Fix: Re-authorize the Gong connection (Gong admin completes OAuth again in Settings → Integrations).
- 403 Forbidden — Insufficient scopes or API access. Fix: Ensure the OAuth app in Gong Admin Center has the required authorization scopes; reconnect if scopes were updated.
- No calls returned / “Access denied” for a call — User’s Gong permission profile limits which calls they can see (own, team, reports, or all). Fix: This is expected; users only see calls their Gong profile allows. Admins can adjust permission profiles in Gong.
- User not in company hierarchy —
get_gong_user_details may fail if the user ID is not in the workspace hierarchy. Fix: Ensure the user exists in Gong and the request uses the correct Gong user ID.
- Engage flow not found — Flow owner email or workspace may be wrong. Fix: Use the flow owner’s email or user ID from Gong; optionally specify workspace_id.
Support
