Articles on: Integrations

Webhook integration: How to set it up in Nimbata

Nimbata’s Webhook integration allows you to send call data to a custom HTTP endpoint, helping you connect Nimbata with your internal systems or third-party tools. This guide covers how to configure webhooks and control which call data fields are sent when events occur.

To do so follow the steps described below:

How to set up your Webhook integration

Note: Webhooks are delivered on a best-effort basis. If the receiving endpoint is unavailable or returns an error, the payload may not be delivered.

Step 1. Go to Integrations > Webhook.

Select the trigger that establishes the criteria for determining when Nimbata should transmit call data to your specified endpoint. You can choose the default one "After Every Call" or create your own based on your needs. Triggers are evaluated after the call is completed, not while the call is in progress.

Step 2. Integrate with your custom endpoint by entering the URL. Nimbata sends an HTTP POST request with a JSON payload to this URL whenever the trigger conditions are met.

Step 3. Select the authorization method (if authorization is required) and then input the required credentials. You can also create additional (custom) parameters for an even more detailed overview of your call data.

Tip: Supported authorization methods apply only to the outgoing request headers. Nimbata does not handle endpoint-side authentication logic.

Step 4. It's time to choose the call data you wish to receive. The following list shows the most common call data our users prefer to include in their webhooks.

You can easily remove a value by clicking on the cross symbol or change the default title. If you wish to add a value, click on the "+" symbol and complete the required fields accordingly.

Important:

Renaming fields only changes the key name sent in the payload.
Removing or renaming fields may break downstream automations that expect a fixed schema.

Step 5. Test your integration. If your setup is correct, a successful message will appear. Then, click on "Save".

Note: The test sends a sample webhook payload and does not represent a real call event.

Tip: Make sure your endpoint responds with a successful HTTP status code (2xx). Non-successful responses may prevent successful delivery.

🎉 That's it, you're all set! Whenever a call is made and meets the criteria set by your trigger, Nimbata will automatically dispatch the selected call data to your custom endpoint!

Updated on: 16/02/2026

Was this article helpful?

Thank you!