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 | ## How do I set up custom OAuth credentials for Gong? |
| 2 | |
| 3 | Use your own Gong OAuth integration when you want users to see your integration's name on the consent screen and control the credentials yourself. You need a Gong account with access to the **Admin center**; if you don't see it, ask your Gong workspace admin. |
| 4 | |
| 5 | ### Create the Gong integration |
| 6 | |
| 7 | 1. Sign in to Gong, expand the left sidebar, and click **Admin center** at the bottom. |
| 8 | 2. In the **Ecosystem** section, click **API**, then switch from the **API Keys** tab to the **Integrations** tab. OAuth apps live under **Integrations**. |
| 9 | |
| 10 |  |
| 11 | 3. Click **Create Integration** and fill in the name, description, short description, and logos. |
| 12 | |
| 13 |  |
| 14 | 4. Under **Required authorization scopes**, select the scopes your integration needs (see Scopes below). |
| 15 | |
| 16 |  |
| 17 | 5. In **Redirect URI**, enter `https://backend.composio.dev/api/v1/auth-apps/add` with no trailing slash. It must exactly match the `oauth_redirect_uri` field in your Composio auth config. Fill in the remaining required fields (privacy and terms links, help article, contact email, domain). |
| 18 | 6. Click **Save**. Back on the **Integrations** list, copy the **Client ID** from the table, then click **Show secret** in the **Client Secret** column and copy the secret. Store it now; if you lose it, regenerate it from the integration's menu and update your auth config. |
| 19 | 7. Add Composio's IP addresses to the integration's trusted IP lists, as described in the IP allowlist question below. |
| 20 | |
| 21 | ### Create the auth config in Composio |
| 22 | |
| 23 | 1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Gong**. |
| 24 | 2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**. |
| 25 | 3. Paste the **Client ID** and **Client Secret**, enter the same scopes you selected in Gong, then create the auth config. |
| 26 | 4. Click **Connect Account**. When asked for the API base URL, keep `https://api.gong.io` unless your Gong admin gives you a tenant-specific address such as `https://company-17.api.gong.io`. Don't use the web app URL from your browser (for example `us-12345.app.gong.io`). |
| 27 | |
| 28 |  |
| 29 | 5. Review the permissions on Gong's consent screen, click **Allow**, and confirm the account shows as **Active**. |
| 30 | |
| 31 | See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. |
| 32 | |
| 33 | ### Scopes |
| 34 | |
| 35 | The scopes in the auth config must match the scopes selected in the Gong integration. If they differ, authorization fails or tools return permission errors; add any missing scope to both places and reconnect. The default auth config requests a broad set covering calls, meetings, CRM, users, flows, and stats. Common choices include `api:calls:read:transcript`, `api:calls:create`, `api:users:read`, `api:meetings:user:create`, and `api:workspaces:read`. Request only what your integration uses, since users see the full list on the consent screen. |
| 36 | |
| 37 | ## Which IP addresses should I allowlist for Gong OAuth? |
| 38 | |
| 39 | Gong now requires every OAuth integration to have trusted IP addresses configured. Gong's [release notes](https://help.gong.io/docs/release-notes#planned-change-management) list this change as announced in September 2026, with release in October 2026. If Gong gave your integration an October 15, 2026 deadline, add these IPs before that date. |
| 40 | |
| 41 | If you use your own Gong OAuth integration with Composio, add all four Composio IPs to both the **Access Token** and **Refresh Token** trusted IP lists: |
| 42 | |
| 43 | - `52.72.72.59/32` |
| 44 | - `54.243.138.89/32` |
| 45 | - `54.224.131.195/32` |
| 46 | - `34.233.50.61/32` |
| 47 | |
| 48 | Composio's traffic to Gong can come from any of these addresses. If you add only some of them, or add them to only one list, API calls or token refreshes can fail intermittently. The same list applies to every service; see [Composio outbound IP addresses](/docs/security/outbound-ips). |
| 49 | |
| 50 | For setup steps, see Gong's guide to [adding trusted IPs to your integration](https://help.gong.io/docs/configure-trusted-ips-for-your-integration). |