# Webhooks and Zapier
Nimbata's Webhook integration sends call, form or SMS data to any HTTP endpoint, letting you connect Nimbata with internal systems or third-party tools that accept POST requests. The Zapier integration connects call activity with hundreds of apps, and the Cometly integration connects phone leads with your marketing attribution reporting.
## Webhooks
> **Note:** Webhooks are delivered on a best-effort basis. If your endpoint is unavailable or returns an error, the payload may not be delivered.
1. **Select your trigger**
- Go to [Integrations > Webhook](https://app.nimbata.com/integrations/webhook).
- Under **Type of data to send**, choose **Call** (or **Form** or **SMS**).
- Which calls are sent is decided by a workflow with a Webhook action: a workflow that runs when a call ends, with no filter, sends every call, and its filters define specific criteria.
- A workflow on **Call Ends** runs after the call ends, not during it.
Detailed guide: [Create a workflow](https://help.nimbata.com/workflows/workflows#create-a-workflow)
2. **Enter your endpoint URL**
- In the **Destination** section, enter the URL of your endpoint in **Endpoint URL (https only)** (1).
- Nimbata sends an HTTP POST request with a JSON payload to this URL whenever the workflow sends a call.
[The Webhook integration page with one webhook open: Type of data to send set to Call, the Destination section with the Endpoint URL (https only) field marked 1, and the Authentication and Payload sections closed]
*In Destination, enter your Endpoint URL (1). Authentication and Payload follow.*
3. **Set authorization**
- In the **Authentication** section, select the **Authorization method** if your endpoint requires it (**Other**, **API key**, **Bearer Token** or **Basic Auth**) and enter the credentials.
- An **API key** can be added to the request header or to the URL's query string (**Add to**). The optional authorization parameters can go in either place too.
- Changing the **Endpoint URL** clears the saved credentials, so enter them again afterwards.
4. **Choose your payload fields**
- In the **Payload** section, select the call data fields to include in the payload.
- Use **✕** to remove a field.
- Type in the name box to rename it.
- Alternatively, click **Add parameter** (1) to add fields.
- Check **Wrap payload in a 'data' object** to send the fields inside a `data` object.
[The Payload section with Parameter name and Value rows for utm_source, utm_medium, utm_campaign, ga_cid and call_duration, the Add parameter button marked 1, and the Wrap payload in a data object box]
*Each row maps a parameter name to a Nimbata value. Add parameter (1) adds a row.*
> **Tip:** Renaming a field only changes the JSON key name. Removing or renaming fields can break downstream systems that expect a fixed schema.
5. **Test and save**
- Once the webhook has an endpoint URL and has been saved, click **Send Test** at the bottom of it. Check or change the sample values, then click **Send event**: Nimbata shows your endpoint's HTTP response code.
- For call webhooks, when Google Analytics 4 is set up, you can also tick **Use GA4 request body** to send the payload in GA4's format.
- Nimbata saves your changes as you make them.
> **Warning:** Your endpoint must respond with a 2xx HTTP status code. The test sends a sample payload, not a real call event.
🎉 Done! Whenever a call meets your trigger criteria, Nimbata POSTs the selected call data to your endpoint.
## Zapier
Nimbata's Zapier integration lets you connect call activity with hundreds of apps, CRMs, reporting tools, and more, using automated workflows called Zaps.
1. **Start your Zap**
- Go to [Integrations > Zapier](https://app.nimbata.com/integrations/zapier).
- Browse the pre-built integration tiles.
- Alternatively, search for the app you want to connect.
- Then click the tile to open Zapier.
> **Tip:** If you don't have a Zapier account, create a free one; it takes just a few minutes.
2. **Configure the Nimbata trigger**
In Zapier:
- Set **Nimbata** as the trigger app, and the event: a new call, or a new form submission.
- Connect your Nimbata account using the API keys found on the [Zapier integration page](https://app.nimbata.com/integrations/zapier).
- Then test the trigger to confirm Zapier receives call data.
The **API Key** and **API Secret** are shown only to people who can manage the project's Zapier setup. Anyone else sees a note in their place: ask someone who manages it to connect Zapier, or to give you that permission.
3. **Configure your action**
- Select the destination app.
- Choose the event that should happen after a call (for example, create a contact or add a row).
- Connect your account.
- Map the Nimbata fields to the destination fields.
- Test the action to confirm data flows correctly.
- Finally, click **Publish Zap**.
4. **Add Zapier to a workflow**
- Go back to Nimbata, to [Integrations > Zapier](https://app.nimbata.com/integrations/zapier).
- The Zapier page has no trigger setting: a workflow decides which calls or forms fire the Zap. In the panel at the top, click **+ Create** for a new workflow, or **Manage workflows** to add Zapier to an existing one.
🎉 Done! Make a test call to confirm data appears in your connected app.
Detailed guide: [Create a workflow](https://help.nimbata.com/workflows/workflows#create-a-workflow)
## Cometly
Nimbata's Cometly integration sends call data to Cometly, so you can connect phone leads with your marketing attribution reporting.
1. **Open the Cometly integration in Nimbata**
- Go to [Integrations > Cometly](https://app.nimbata.com/integrations/cometly).
- Leave the **Cometly URL:** field open. You paste the Cometly webhook URL into it in the next step.
[The Cometly integration page with an empty Cometly URL field, marked 1]
*The Cometly URL field (1) waits for the webhook URL from Cometly.*
2. **Generate the webhook URL in Cometly**
- In Cometly, go to [Integrations](https://app.cometly.com/integrations).
- Scroll to **Connections** and click **Add Integration**.
- Search for and select **Nimbata**.
- Click **Next**, then click **Activate Nimbata**.
- Copy the webhook URL that is generated.
3. **Paste the URL in Nimbata and test**
- Paste the webhook URL into the **Cometly URL:** field in Nimbata.
- Optionally, click **Send Test** (it appears beside the field once a URL is in) > **Send Event** to verify that call data appears in Cometly as expected.
🎉 Done! Your Nimbata account is now integrated with Cometly.
Updated November 11, 2026
Nimbata’s Webhook integration sends call, form or SMS data to any HTTP endpoint, letting you connect Nimbata with internal systems or third-party tools that accept POST requests. The Zapier integration connects call activity with hundreds of apps, and the Cometly integration connects phone leads with your marketing attribution reporting.
Webhooks
Note
Webhooks are delivered on a best-effort basis. If your endpoint is unavailable or returns an error, the payload may not be delivered.
Under Type of data to send, choose Call (or Form or SMS).
Which calls are sent is decided by a workflow with a Webhook action: a workflow that runs when a call ends, with no filter, sends every call, and its filters define specific criteria.
A workflow on Call Ends runs after the call ends, not during it.
In Destination, enter your Endpoint URL (1). Authentication and Payload follow.
Set authorization
In the Authentication section, select the Authorization method if your endpoint requires it (Other, API key, Bearer Token or Basic Auth) and enter the credentials.
An API key can be added to the request header or to the URL’s query string (Add to). The optional authorization parameters can go in either place too.
Changing the Endpoint URL clears the saved credentials, so enter them again afterwards.
Choose your payload fields
In the Payload section, select the call data fields to include in the payload.
Use ✕ to remove a field.
Type in the name box to rename it.
Alternatively, click Add parameter (1) to add fields.
Check Wrap payload in a ‘data’ object to send the fields inside a data object.
Payload
Select the data included in each request.
Complete
Parameter nameValue
utm_sourceUTM Source
✕
utm_mediumUTM Medium
✕
utm_campaignUTM Campaign
✕
ga_cidGoogle Analytics Customer ID
✕
call_durationCall Duration
✕
Add parameter1
Wrap payload in a 'data' object (i.e.: {"data":"PAYLOAD"})
Each row maps a parameter name to a Nimbata value. Add parameter (1) adds a row.
Tip
Renaming a field only changes the JSON key name. Removing or renaming fields can break downstream systems that expect a fixed schema.
Test and save
Once the webhook has an endpoint URL and has been saved, click Send Test at the bottom of it. Check or change the sample values, then click Send event: Nimbata shows your endpoint’s HTTP response code.
For call webhooks, when Google Analytics 4 is set up, you can also tick Use GA4 request body to send the payload in GA4’s format.
Nimbata saves your changes as you make them.
Warning
Your endpoint must respond with a 2xx HTTP status code. The test sends a sample payload, not a real call event.
🎉 Done! Whenever a call meets your trigger criteria, Nimbata POSTs the selected call data to your endpoint.
Zapier
Nimbata’s Zapier integration lets you connect call activity with hundreds of apps, CRMs, reporting tools, and more, using automated workflows called Zaps.
Then test the trigger to confirm Zapier receives call data.
The API Key and API Secret are shown only to people who can manage the project’s Zapier setup. Anyone else sees a note in their place: ask someone who manages it to connect Zapier, or to give you that permission.
Configure your action
Select the destination app.
Choose the event that should happen after a call (for example, create a contact or add a row).
The Zapier page has no trigger setting: a workflow decides which calls or forms fire the Zap. In the panel at the top, click + Create for a new workflow, or Manage workflows to add Zapier to an existing one.
🎉 Done! Make a test call to confirm data appears in your connected app.
