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

# How DialNexa Agent Webhooks Reach Your Endpoint

> Connect the agent webhook toggle to a workspace URL, verification secret, and delivery logs so call events reach your endpoint.

This page explains how the per-agent webhook settings fit into the workspace webhook system. For the controls themselves - where they live and how to use them - see [Agent Webhooks in Agent Settings](https://dialnexa.com/docs/agent-settings/agent-webhooks.md).

> [!TIP]
>
> Think of it as three parts: the agent's switch and destination pick, the workspace's named webhooks, and the signing secrets your receivers verify with.

## DialNexa Agent Webhook Delivery Layers

Each layer has a different owner. Events flow only when all three are in place: the agent's toggle is on with a destination webhook picked, that webhook is active with a valid URL, and the receiver verifies with the webhook's signing secret.

| Layer | Configured in | Purpose |
| - | - | - |
| Agent toggle and destination | [Agent Settings](https://dialnexa.com/docs/agent-settings/agent-webhooks.md) | Enable events for a saved agent and pick which webhook they go to. |
| External webhooks | [Webhooks page](https://dialnexa.com/docs/api-access/external-webhooks.md) | Named endpoints, each with its own URL and signing secret. One webhook can serve any number of agents. |
| Webhook secrets | [Signing secrets](https://dialnexa.com/docs/api-access/webhook-secrets.md) | Let your receiver verify events. One secret can sign several webhooks. |
| Delivery Ledger | [Webhook delivery system](https://dialnexa.com/docs/api-access/webhook-retries-and-failures.md) | Per-call history with status, errors, retries, and payload download. |

## Agent Webhook Confusions

> [accordion] The agent toggle is on but no event arrives
>
> Check which webhook the agent points at, that webhook's active state and URL, its signing secret, and your receiver logs. The webhook's Delivery Ledger shows whether DialNexa attempted delivery.

> [accordion] The receiver rejects events
>
> Check secret rotation and verification code. During a rotation grace window, verify against any configured key.

> [accordion] Two agents report to different systems
>
> Point each agent at a different webhook. Events from one agent only reach the single webhook it is attached to.

> [accordion] The wrong agent triggers events
>
> Confirm which agent version handled the call. The payload's `agent_id` identifies the agent on every event.

## Related Reading

> [card] [Agent Settings Webhook](https://dialnexa.com/docs/agent-settings/agent-webhooks.md)
>
> Use the builder toggle.

> [card] [External Webhooks](https://dialnexa.com/docs/api-access/external-webhooks.md)
>
> Configure receiver URL.

> [card] [Webhook Secrets](https://dialnexa.com/docs/api-access/webhook-secrets.md)
>
> Verify events.


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