
Connect
Gong takes two steps, and the first one on its own does nothing.Authorise
Click Connect on the Gong card and approve Squad in Gong. Squad asks for read access to calls and transcripts.
Create the webhook rule
The connection now sits at Setup required in amber, with a Finish setup button on the card. The detail page has a webhook URL to copy. In Gong, create a webhook automation rule that fires to that URL with a Signed-JWT header. Gong shows a public key when you save the rule. Paste it into Verification public key in Squad and save.The status flips to Connected once the key is stored. Squad verifies every inbound webhook against that key, so until it’s there Gong’s deliveries are rejected.
Triggers
One trigger, Call recorded. It fires for every call your Gong rule matches, so the rule in Gong is where you decide which calls count (a team, a deal stage, a call type). There’s no per-call filter inside Squad.Two kinds of delivery never produce a run. Test payloads from Gong’s rule editor are acknowledged and ignored. Private calls are skipped, whether Gong marks the payload private or the call’s own metadata does.
Tools
- Read
- Write
This is the step that turns a call into signals. It comes with the Gong trigger, so an agent triggered on a recorded call always has it. Pass a call ID to capture a different call. Repeat captures of the same call ID are deduped, and a call with an empty transcript is skipped rather than stored.
