> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/gong.md).

# Gong Engage

Use Gong Engage Assign Flow for a prospect Gong already knows through the CRM.

## Connect

An admin opens **Settings → Integrations → Gong Engage** and enters the **Access key**, **Access key secret** and **API base URL** for the account.

Saving lists a user to verify the key pair. It does not assign a flow or change a prospect.

## Configure Assign Flow

1. Map the **Sending user** email. This is the Gong user who owns the flow instance and its to-dos.
2. Choose the **Flow** available to that user.
3. Map the **CRM record ID** of the lead or contact Gong knows.

An email address is not accepted as the CRM prospect ID. Match or create the CRM prospect earlier and ensure Gong can resolve it.

## Verify

Inspect the flow, prospect and returned status. Confirm a controlled live assignment in Gong Engage.

If no flows load, check the chosen sending user and their access. If assignment fails, check the provider key pair, API base, CRM synchronization and prospect identifier.

Map the Distro assignee to the intended Gong identity when routing and sending should belong to the same person. See [Connected identities](/settings/identities.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/integrations/gong.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.