Connect Gong to Teamwork Graph

Make all your sales calls searchable alongside your company knowledge.

What is indexed?

The Gong connector indexes these objects:

  • Gong calls

  • Transcripts (including duration, participants, topics)

  • CRM data (if connected): Display names of accounts and deals

  • Folders (structure and permissions for call recordings)

  • Workspaces

  • Users and their permissions

Before you begin

The Gong connector controls what data is synced from Gong into Atlassian for indexing and search. It indexes every meeting in Gong by default.

  • Review your permissions in Gong before starting.

  • You must have Technical admin permissions in Gong to connect Gong to the Teamwork Graph.

  • When you access Gong data through Rovo, your own Gong access is used.

Permissions required

Connecting Gong requires the Gong API v2 permissions listed below. A Gong Technical Admin must grant these permissions when you set up the connector in admin.atlassian.com.

  • api:calls:read:basic

  • api:calls:read:media-url

  • api:library:read

  • api:users:read

  • api:calls:read:extensive

  • api:permission-profile:read

  • api:call-user-access:read

  • api:call-outcomes:read

  • api:calls:read:transcript

  • api:workspaces:read

Connect Gong to Teamwork Graph

Who can do this?
Role: Organization admin
Atlassian Cloud: Standard, Premium, and Enterprise plans
Atlassian Government Cloud: Not available

To connect Gong to Teamwork graph:

  1. Go to Atlassian Administration. Select your organization if you have more than one.

  2. From the side navigation, select Connectors.

  3. Select Add connector.
    If you have more than one site, select the site you want to connect.

  4. Select Gong, then select Next.

  5. Enter a Connector name.
    We recommend using “Gong (Synced) Connector for Atlassian Teamwork Graph.”

  6. Get your API base URL. You can find this in the Gong Admin Center under API in the Create an API Key section.
    The URL typically follows the format https://<REGION>.api.gong.io. Ensure you use api and not app in the URL.

  7. (Optional) Enter the number of days for Call retention.
    If you leave this blank, it may default to 3 years. You can find your current policy in the Gong Admin Center under Data protection and privacy then Retention policy.

  8. (Optional) Enter your Salesforce base URL.
    If you use the Salesforce connector for Rovo, this URL allows the Teamwork Graph to associate Gong calls with Salesforce accounts and deals. The format is typically https://yourdomain.my.salesforce.com.

  9. Select Authorize Gong.

  10. Follow the prompts in Gong to accept the permissions for the Rovo app and complete the authorization flow.

Next steps

After you’ve finished connecting Gong:

  1. Gong calls will appear in Search results incrementally over the next few hours. Once the admin authenticates, users do not need to connect individually to see results.

  2. The time required to complete the initial data ingestion depends on the number of objects in your Gong instance.

  3. To use Gong in Chat and Agents, connect to the remote Gong MCP server. Gong MCP tools are currently only available to paid Gong users and may consume Gong AI credits.

To connect the MCP server:

  1. Go to the Gong Admin center. Under Ecosystem, select MCP.

  2. Select the MCP Server tab, then select New MCP server integration.

  3. Under Integration Name, enter Gong MCP (or your preferred descriptor).

  4. Under Redirect URL, paste https://id.atlassian.com/outboundAuth/finish.

  5. Under Registration Type, select Automatic.

  6. Under Authorization Context, select Personal access.

  7. Select Save, then select Done. Verify the integration appears on the MCP Server page.

  8. Return to Atlassian Administration. From the side navigation, select Apps.

  9. Under Sites, select your site, then select Connected apps.

  10. Select the Explore apps list, then select Add external MCP server.

  11. Select Gong.

  12. Under MCP server name, enter Gong MCP (or your preferred descriptor).

  13. Select Authenticate, then Allow.

 

Still need help?

The Atlassian Community is here for you.