Skip to main content
DialNexa external webhooks send real-time call events to HTTPS endpoints you control. A workspace can hold several named webhooks, each with its own URL, signing secret, retry count, and request timeout. Manage them under Workspace Settings, Developer, Webhooks, and point each agent at the webhook its events should reach.
The webhook URL must start with https://. Webhooks are not the place to experiment with almost-secure endpoints.

​
External Webhook Fields

These fields control event delivery for each webhook.

​
Events And Delivery

Each webhook’s Delivery Ledger shows its full delivery history.

Verification

Reachability check sent before a webhook is saved.

Call initiated

Event sent when a call starts.

Call ended

Event sent when a call ends.

Transfer completed

Event sent for completed transfer behavior.

Delivery Ledger

Per-call history with statuses, retries, errors, and payload download.

​
Create A Webhook Receiver

1

Create a webhook secret

Configure verification before relying on events. Several webhooks can share one secret.
2

Choose Add webhook

Name it after the system it feeds, such as CRM Sync.
3

Enter HTTPS URL and pick the signing secret

Use a stable endpoint under your control and the secret that receiver verifies with.
4

Set timeout and retries

Choose values your receiver can satisfy.
5

Pass the verification request

On save, DialNexa sends a verification POST to your URL and your endpoint must answer with a 2xx status code inside the timeout you set. Anything else blocks the webhook from being created. This payload has no call object, so branch on event_type before reading call fields.
6

Attach the webhook to an agent

In the agent editor’s Webhook section, enable the toggle and pick this webhook as the destination. See Agent Webhooks.
7

Trigger a test call

Confirm the receiver gets and verifies the event, then check the webhook’s Delivery Ledger.

​
Delete Rules

Deleting a webhook detaches it from every agent that pointed at it; those agents stop sending events until you attach another webhook. Deleting a webhook does not affect its signing secret, and events already queued for a deleted webhook are skipped rather than delivered.

Webhook Secrets

Create, rotate, and delete signing secrets.

Agent Webhooks

Route each agent’s events to a webhook.

Webhook Failures

Debug delivery with the Delivery Ledger.