> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kallabot.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhooks

> Send Kallabot events, like a finished call or a new message, to your own software or a workflow, as they happen.

A webhook tells another system about something the moment it happens in Kallabot: a call ended, a summary is ready, a WhatsApp message arrived, an agent was published. Your developer, your CRM or a [workflow](https://docs.kallabot.com/guides/workflows.md) receives it and acts on it.

Find them in **Settings → For developers → Webhooks**.

## Add an endpoint

**1. Click Add endpoint**

Paste the **Endpoint URL**: the web address that should receive events. It must start with `https://`.

**2. Choose events**

Pick **Every event**, or **Choose events instead** and tick the ones you want, grouped as Calls, Chats, Tools, Phone numbers, Agents and Knowledge.

**3. Choose agents (optional)**

Leave **Every agent**, or pick **Chosen agents** to only send events about some of them.

**4. Decide on content**

Turn on **Include content** only if the receiving system needs phone numbers, message text or summaries. Leave it off otherwise.

**5. Save the signing secret**

Kallabot shows a **signing secret** once. Give it to your developer: it proves each event really came from Kallabot.

## Check it works

Click **Send test**. Kallabot sends a sample event straight away and shows what your server answered. If it says **Your server didn't take the test**, open the delivery to see the answer it got.

## The delivery log

**Deliveries** lists every event sent, with each attempt, and refreshes every 15 seconds. Open one to see exactly what was sent and what came back. Click **Retry** to send it again.

## When an endpoint fails

If your server doesn't answer, Kallabot keeps trying for about a day. If it keeps failing for **5 days**, the endpoint turns itself off and the workspace owners get an email. Nothing is lost: events are kept for 30 days.

To recover:

**1. Fix the receiving server**

Make sure it's back up.

**2. Turn the endpoint on**

Click **Turn on**. Its failure count resets.

**3. Replay what it missed**

Click **Replay failed since…** and pick when the trouble started.

## Rotate the secret

If the signing secret may have leaked, click **Rotate secret**. The new secret is shown once. The old one keeps working for 24 hours, so your developer has time to switch.

> [card] [For developers](https://docs.kallabot.com/developers/webhooks.md)
>
> Signature verification code, retry schedule, the full event catalogue and the webhooks API.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.