Gong setup

Configuration and setup for the Gong connector are performed in the Glean Admin/Connectors console. Most steps are automated with onscreen instructions.

Requirements

The following requirements must be met for successful deployment and operation of the Gong connector.

Technical requirements

• Customer must use Gong’s cloud service.
• Glean must have access to the customer’s Gong instance over the internet (no firewall restrictions blocking the Gong API).

Credential requirements

• OAuth 2.0 credentials are required for authentication. An admin user in Gong must perform the authentication flow to authorize data access.

Permission requirements

• The authenticating Gong user must be an admin in Gong
• Access must be sufficient to read: users, permission profiles, workspaces, folders (library), calls, call transcripts, and metadata
• The connector implements Gong’s permission model; only users with access to data in Gong will have access to corresponding items in Glean

Authentication and credentials

• In the deployment console, navigate to the Gong connector setup page.
• Click the provided link to start the OAuth 2.0 authorization process with the Glean-Gong integration app.
• Authenticate with Gong using the admin account credentials.
• Upon successful authorization, required credentials are securely stored and Glean is authorized to access the Gong API for crawling.

Step-by-step setup

1. Log in to the Glean deployment console as an admin.
2. Navigate to the Connectors section.
3. Begin setup for the Gong connector by following the setup wizard.
4. Click the link presented to initiate OAuth 2.0 authorization with Gong.
5. Log in to Gong as an admin to grant consent.
6. After setup is complete, Glean will begin crawling Gong content and permissions at regular intervals.
7. (Optional) Configure which users or groups should be able to view Gong search results in Glean, as needed for your organization’s policies.

Glean processes and ingests data and permissions according to Gong’s model and reflects permissions changes promptly—if a user's access changes in Gong, this is updated in Glean during the next crawl cycle.