Connect Gong to subscribe to the call.analyzed webhook. Every analyzed call streams to FastFollow with full transcript and metadata, triggering AI follow-up generation.
Technical Admin access required
Only a Gong Technical Admin can create the OAuth client and grant the required scopes. Loop them in before starting this setup.
~15 minutes plus Gong-side approval
In your Gong Technical Admin → API Integration → Generate OAuth client. This is the application FastFollow will use to authorize against your Gong workspace.
Gong scopes must be explicitly enabled on the OAuth client by your Gong admin.
In FastFollow → Integrations → Gong → Connect. The first user to connect from a workspace acts as the workspace owner of the integration.
What Gong pushes to FastFollow
call.analyzedFires when Gong finishes analyzing a call (typically 5–15 minutes after the call ends). FastFollow fetches the full transcript via the Gong API and triggers follow-up generation. Signature verified via the workspace-scoped subscription token.
The most common Gong errors
unauthorized_clientInitial OAuth handshake fails.
Fix: The Gong OAuth client has not been approved by Gong support. New OAuth clients require activation — contact your Gong CSM if you cannot complete the auth flow.
forbidden (transcripts)Calls list correctly but transcript fetch fails with 403.
Fix: The api:calls:read:transcript scope was not granted. Have your Gong Technical Admin add it to the OAuth client, then reconnect from FastFollow.
webhook_subscription_failedConnection completes but no call.analyzed events arrive.
Fix: FastFollow tries to register the webhook automatically but it can fail if the workspace already has a conflicting subscription. Check FastFollow → /admin/health → Gong subscriptions, and resubscribe manually if needed.
rate_limitBulk historical backfill returns 429.
Fix: Gong rate-limits at 3 requests/second per OAuth client. FastFollow honors Retry-After. For large workspaces, schedule the initial sync during off-hours.