Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Gong" |
| 4 | description: "Public support knowledge for Gong." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "gong" |
| 10 | --- |
| 11 | # Gong |
| 12 | |
| 13 | |
| 14 | ## Gong base URL differs by customer and should be provided at connection time |
| 15 | |
| 16 | Gong's base URL can differ per user/customer. Avoid hardcoding a single Gong base URL in a shared auth config for all users; collect and pass the user's `gong_url`/base URL when initiating the connected account. |
| 17 | |
| 18 | ## Gong connection initiation can use Basic auth fields: access key, access key secret, and Gong URL |
| 19 | |
| 20 | For Gong Basic auth, collect the access key as username, access key secret as password, and the customer's Gong URL/base URL. Pass those fields when initiating the connected account; hosted auth can also collect required fields for the customer instead of manually building the frontend form. |
| 21 | |
| 22 | ## Gong MCP tool scopes can be read from tool annotations in the tools API |
| 23 | |
| 24 | For Gong MCP tools, scopes were exposed through the `annotations` field from the `listTools` API per the newer MCP spec. If a customer needs to reason about Gong scopes, inspect tool annotations from the tools API instead of relying only on static docs. |