---
title: "Send data to a webhook"
description: Configure an HTTPS address to receive each captured record when it becomes complete.
---

If you need captured data to reach another system —for example, your CRM—, you can enable a webhook per agent. TukiAssistant notifies you over HTTPS every time a captured record becomes complete, retrying until it is confirmed.

:::note[Before you start]
You need the editor or admin role in the workspace. The webhook sends personal data (for example, name and email): use a secure HTTPS address and check with your technical team that the receiving system verifies the signature.
:::

## Configure the webhook

1. **Open the agent**

    Open **Agents** in the sidebar and go to the agent.

2. **Open webhooks**

    Go to the **Connections** tab and open **Webhooks**.

3. **Enter the destination URL**

    In the **Captured record webhook** card, enter your system's **Destination URL (HTTPS)**.

4. **Generate and copy the secret**

    Click **Generate secret**, then **Copy secret**, and save it in your receiving system. The secret cannot be shown again.

5. **Turn on delivery**

    Turn on **Enable captured record delivery**.

6. **Save the webhook**

    Click **Save capture webhook**.

Every delivery carries a signature made with that secret; the receiving system must verify it to confirm the message comes from TukiAssistant. Each record has a stable identifier (it starts with `cap_`); use it to avoid duplicates if a delivery is retried.

## How delivery works

- Only records that **become complete** are sent; the playground and the public test link never send anything.
- Enabling the webhook does not resend older records: it applies to records completed from that moment on.
- If your system does not respond, TukiAssistant retries. On the card you can check the status with **Refresh status**: pending, delivered, errored, and paused.
- If you disable the webhook, pending deliveries stay paused until you enable it again. If you change the URL, pending deliveries for the previous address stay paused and are not sent to the new one.

:::tip
If you see delivery errors, check that the URL responds correctly and that the secret configured in your system is the latest one you generated.
:::

## Next steps


**[Capture customer data](/en/conversations/capture-customer-data)**

Configure a table so your agent saves data like name, email, or phone during conversations.

**[Review and manage captured data](/en/conversations/manage-captured-data)**

View, filter, export, and delete the records your agents saved during conversations.
