> ## 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.

# DialNexa Agent Webhooks

> Understand DialNexa agent webhooks, the Enable Webhook toggle, save-first behavior, webhook IDs, and workspace external webhook requirements.

DialNexa agent webhooks let an agent participate in real-time event delivery. In the agent settings panel, users can enable or disable the webhook toggle for a saved agent. This page covers the per-agent toggle only; the workspace webhook URL, secret, and delivery behavior live in [External Webhooks](/api-access/external-webhooks) and [Webhook Secrets](/api-access/webhook-secrets).

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/agent-webhook-panel.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=ec1762bc51c5976fbe018c75b04c69ab" alt="DialNexa agent settings Webhook panel showing the Enable Webhook toggle for a saved agent." style={{ width: '100%', maxWidth: '800px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="686" height="1070" data-path="images/documentation/screenshots/agent-webhook-panel.png" />

<Tip>
  Agent webhook is the switch on the agent. External webhook is the address and verification setup. Both matter if you want events to arrive somewhere useful.
</Tip>

## Agent Webhook Behavior

The toggle updates webhook state for the selected agent.

| Action                 | Behavior                                                                                           |
| ---------------------- | -------------------------------------------------------------------------------------------------- |
| Enable Webhook         | Creates or assigns webhook state for the agent and stores the webhook id.                          |
| Disable Webhook        | Removes the agent webhook association.                                                             |
| Save first requirement | If the agent has not been saved yet, the dashboard asks the user to save before enabling webhooks. |
| Failure handling       | If the update fails, the toggle does not stay enabled.                                             |

## What Else Must Be Configured

Agent webhooks are only one part of event delivery.

<CardGroup cols={2}>
  <Card title="External webhook URL" icon="webhook" href="/api-access/external-webhooks">
    The workspace endpoint receives events and must use HTTPS.
  </Card>

  <Card title="Webhook secret" icon="key-round" href="/api-access/webhook-secrets">
    The receiver should verify events with the workspace webhook secret.
  </Card>

  <Card title="Delivery retries" icon="refresh-cw" href="/api-access/webhook-retries-and-failures">
    Workspace webhook settings decide retry count and timeout.
  </Card>

  <Card title="Call evidence" icon="activity" href="/monitoring/call-history">
    Call History confirms what happened even if a receiver failed.
  </Card>
</CardGroup>

## Enable Agent Events Safely

<Steps>
  <Step title="Create the receiver first">
    Configure the external webhook endpoint and secret.
  </Step>

  <Step title="Save the agent">
    The agent must exist before the toggle can update webhook state.
  </Step>

  <Step title="Enable webhook in settings">
    Turn on the agent-level webhook.
  </Step>

  <Step title="Place a test call">
    Confirm the receiver sees the event and Call History shows the same call.
  </Step>
</Steps>

## Related Reading

<CardGroup cols={2}>
  <Card title="External Webhooks" icon="webhook" href="/api-access/external-webhooks">
    Configure the receiver endpoint.
  </Card>

  <Card title="Webhook Secrets" icon="key-round" href="/api-access/webhook-secrets">
    Verify events safely.
  </Card>

  <Card title="Webhook Failures" icon="refresh-cw" href="/api-access/webhook-retries-and-failures">
    Debug delivery issues.
  </Card>
</CardGroup>