How can we help?

Our integration with Gong Engage is designed to streamline your workflows by ensuring the right prospects are enrolled in the right flows with the right context. To achieve this, we request specific permissions that allow us to read necessary data and automate actions within Gong Engage - while maintaining the highest standards of security and data minimization.

Below is a breakdown of the permissions we request and why they are needed:

• api:users:read - Allows the integration to view Gong user information — including user IDs, names, and email addresses. Needed for assigning flows, matching outreach to a specific user, or validating who is allowed to send.
• api:flows:read - Allows the integration to fetch and view Engage flows, including steps, logic, triggers, and status. Useful for confirming what flows exist or reading configuration details.
• api:flows:write - Allows the integration to create, update, or modify Engage flows, including editing steps or activating/deactivating flows. This is the permission that enables programmatic flow management.
• api:crm:integrations:read - Allows the integration to view the CRM connection settings (e.g., which CRM is connected, sync status, field mapping availability). Read-only — no ability to change CRM configurations.
• api:crm:schema - Allows the integration to read the CRM schema — i.e., which objects and fields exist, their types, and structure. Needed to validate fields, map custom fields, or build dynamic variables in flows.

Our integration does not store unnecessary Gong data or make modifications beyond the intended automation actions. We follow strict data handling principles to ensure security, compliance, and minimal data access.

If you have any questions about these permissions, please reach out to our support team.