How to set up webhooks with Gong on Nango

​

How it works

1. A Gong automation rule fires and sends a POST request to your Nango webhook URL.
2. Nango verifies the delivery’s signature (if you’ve configured a public key), then routes the event to the connection identified by the nangoConnectionId query param on the webhook URL — Gong’s payload has no field that identifies a single Nango connection, so this param is required.
3. Nango forwards the event to your app, or triggers a sync.

​

Setup

​

1. Get your Nango webhook URL

​

2. Create an automation rule in Gong

1. Go to Admin Center → Settings → Ecosystem → Automation rules and select + Add Rule.
2. Use the filter icon to set which calls should trigger the rule.
3. In the Action dropdown, keep Fire webhook and paste your Nango webhook URL (with nangoConnectionId) as the Destination URL.
4. Choose an authentication method:
   • Signed JWT header — Gong signs deliveries with an RS256 JWT in the Authorization header. Click Show public key and copy it.
5. Name the rule, test it against a sample call, then enable it.

​

3. Set the public key in Nango

• One connection: paste the public key as the Webhook secret on the Gong integration in the Nango dashboard.
• Multiple connections: each one has its own automation rule and public key, so set each connection’s public key as webhookSecret in that connection’s metadata instead:
  curl -X PATCH "https://api.nango.dev/connections/metadata" \
    -H "Authorization: Bearer <NANGO-API-KEY>" \
    -H "Content-Type: application/json" \
    -d '{
      "connection_id": "<CONNECTION-ID>",
      "provider_config_key": "<INTEGRATION-ID>",
      "metadata": {
        "webhookSecret": "<GONG-PUBLIC-KEY>"
      }
    }'
  
  PATCH merges into any metadata the connection already has; POST on the same endpoint replaces it entirely, so prefer PATCH unless you specifically want to wipe existing metadata. Nango checks the integration-level Webhook secret first and falls back to the connection’s metadata when that’s not set.

​

Handle the webhook

• Forward it to your app — Nango forwards the event to your webhook URL with connection attribution. See External webhook forwarding.
• Process it in a sync — run a sync when the webhook arrives using webhookSubscriptions and onWebhook in a sync script. See Real-time syncs.

​

Payload