Gong
This integration enables Orbb to connect with Gong, allowing access to call recordings, transcripts, and user data from your Gong workspace. The integration uses OAuth2 authentication to securely connect to your Gong account and provide comprehensive access to conversation intelligence data.
Prerequisites
- A Gong account with administrative access
- Permission to authorize OAuth2 applications in your Gong workspace
caution
Only users with admin privileges can perform these actions. Ensure you have the necessary permissions before proceeding.
OAuth Scopes
The following OAuth scopes are required for the integration to function properly:
api:calls:read:basic
api:calls:read:extensive
api:users:read
api:calls:read:transcript
OAuth Scopes Explanation
Here's what each scope enables:
-
Call-related scopes:
api:calls:read:basic: View basic call metadata including call IDs, dates, durations, and participantsapi:calls:read:extensive: View detailed call information including advanced analytics, topics, and action itemsapi:calls:read:transcript: Access full call transcripts for analysis and review
-
User-related scopes:
api:users:read: View basic information about users in your Gong workspace
Integration Steps
1. Start OAuth2 Authorization
- In your Orbb dashboard, navigate to Admin Center → Calls Integrations → Gong.io
- Click Connect
- You will be redirected to Gong's authorization page
2. Authorize Orbb
- Review the requested permissions (scopes)
- Click Allow to authorize Orbb
- You will be redirected back to Orbb with the integration configured
tip
After authorization is complete, click the Test button to verify the connection. A green icon will appear if everything is working correctly.
Security Considerations
- The OAuth2 connection is secure and can be revoked at any time from your Gong workspace settings
- Orbb uses token-based authentication and does not store your Gong user credentials
Troubleshooting
If you encounter any issues:
- Verify that the OAuth2 authorization was successful
- Ensure your Gong account has the necessary administrative privileges
- Verify that the required scopes were granted during authorization
- Try disconnecting and reconnecting the integration if issues persist