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

# Custom Webhook

> POST conversation events to your HTTPS endpoint with optional authentication

Custom Webhook sends updates about conversations to a web address you control. Use it when you are not using Zapier or a customer management system. For example, you can send a message to your own order system whenever a conversation ends.

This connection does **not** pull contacts into lists. If you want Botcadence to bring contacts in from another system, use HubSpot or LeadSquared.

## Prerequisites

* An HTTPS endpoint that can receive POST JSON
* Optional: bearer token, custom headers, or an HMAC signing secret, depending on how you authenticate
* Permission to add integrations on the project

## Connect

<Steps>
  <Step title="Open Add Integration">
    In the project sidebar, select **Integrations**, then **Add Integration**. Select **Connect** on the **Custom Webhook** card.
  </Step>

  <Step title="Enter endpoint and auth">
    On **Connect webhook**, fill in:

    * **Webhook URL** — HTTPS URL, for example `https://example.com/hooks/botcadence`
    * **Authentication** — **None**, **Bearer token**, **Custom headers**, or **HMAC signature**
    * **Bearer token** — if you chose bearer
    * **Custom headers** — if you chose headers (JSON object of header names and values)
    * **Signing secret** — if you chose HMAC
  </Step>

  <Step title="Wait for validation">
    The wizard checks that the URL is reachable. When it succeeds, you see **Webhook Connected!**
  </Step>
</Steps>

## Verify

On **Integrations**, the row shows **Connected**.

<Check>
  Attach this connection on a test campaign, inbound, or channel, complete a conversation, and confirm your endpoint received a POST.
</Check>

## Use it

Open the campaign, inbound, or channel **Integrations** tab. Set **Destination** to this webhook connection.

The success screen in the wizard also tells you to attach the connection on a campaign, inbound, or channel export. Events do not fire from the Integrations page alone.

## Limits

* URL must be HTTPS.
* Custom headers must be valid JSON when that auth type is selected.
* This destination competes with Google Sheets, Zapier, and CRM on the same source: one extra destination at a time.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Validation fails">
    Confirm the URL is HTTPS, publicly reachable, and returns a success response to the check. Firewalls that block Botcadence will fail validation.
  </Accordion>

  <Accordion title="No POSTs arrive">
    Attach this connection as **Destination** on the source that actually handled the conversation.
  </Accordion>

  <Accordion title="Your server rejects the request">
    Match **Authentication** to what your endpoint expects. For HMAC, use the same signing secret on both sides.
  </Accordion>
</AccordionGroup>