Create a webhook rule

Prev Next

Silhouette of a person standing, representing human figures in various contexts. Tech admin

Diamond.png Gong Foundation*

Admin center > Settings > Ecosystem > Automation rules

Create a rule defining which calls you want to be sent to another destination. When the rule is triggered, the call data is sent out of Gong to the specified URL.

  1. In the Automation rules page, click + Add Rule to display the create new rule page.

     Rule settings for triggering a webhook on new call.

  2. Click image11.png to filter the calls the rule is applied to.

    1. In the rule filter dialog define the filters for the rule.  For more details on the filters, see Search for calls.

    2. Click SAVE to add the filters to the rule definition.

  3. In the Action dropdown list, the Fire webhook option is selected by default. Define the following:

    1. Destination URL

    2. The authentication method included in the URL:

      • URL includes key: The URL includes a secure random token

      • Signed JWT header: Copy the public key and use it in the webhook to verify the digital signature of the sent data.

        Click Show public key to display and copy it.

  4. Enter a rule name and description.

  5. Test the call as follows.

    1. One call that fits the rule filters is listed for testing. Click Select a different call to test the rule on a different call. A list of eligible calls is displayed. Select the desired call.

    2. Click Test now. You’ll see a success message in green on the top of the screen.

  6. When you are satisfied that the rule is triggered correctly, enable it.

    Toggle switch indicating the rule status is enabled.

For sample code to insert in the receiving destination when using a signed JWT header, see Prepare your receiving application to receive a webhook - JWT header. Also, see what Gong pushes to the Webhook when the rule has been triggered.

Note:

When coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output. It is recommended to future proof your code so that it disregards the JSON fields you don’t use.

*The features available to you depend on your company’s plan and your assigned seats.