This page is usually handled by a technical teammate, even when operations, sales, or support teams decide which events should trigger follow-up work.
What You Configure
Each webhook subscription includes:- Name
- Target URL
- Active/inactive state
- Optional signing secret
- Optional agent scope
- Event subscriptions
Create a Webhook
Review the create form
The create dialog includes destination, signing secret, agent scope, and event selection controls.
Choose agent scope
Optionally restrict the webhook to one or more agents. Leave it empty to receive events for all agents.
Fastest Way to Test
If you are setting up webhooks for the first time, start with a temporary inspection endpoint before you connect your production system.Create a temporary endpoint
Use a request-inspection service such as Webhook.site or RequestBin to get a unique HTTPS URL.
Create a narrow subscription
Subscribe to one or two events only, such as
conversation.ended or conversation.analysis.completed.Trigger a real event
Place a test call or complete the workflow that should emit the selected event.
Inspect the payload
Confirm the headers, signature fields, event type, and
data payload shape before wiring your real endpoint.Implementation Model
The best webhook receivers follow a simple pattern:- verify the signature against the raw body
- acknowledge quickly
- move slow processing into your own background jobs
Event Selection
The event picker is grouped by entity so you can subscribe at different levels:- select or clear all events
- select or clear an entire entity group
- select individual events within a group
Webhook Inventory
The table shows the current subscriptions with:- Name
- Target URL
- Status
- Subscribed event count
- Agent scope
- edit a subscription
- delete a subscription
- verify whether a signing secret is set
Security Recommendations
Use secure HTTPS destinations
Use secure HTTPS destinations
Deliveries should terminate on HTTPS so secrets and event data are protected in transit.
Verify signatures
Verify signatures
Validate the webhook signature and timestamp on every request before you trust the payload.
Keep receiving systems fast
Keep receiving systems fast
Acknowledge the event quickly and move long-running work to your own background jobs.
Separate destinations by purpose
Separate destinations by purpose
Use different webhook subscriptions for CRM sync, analytics, or alerting so you can tune event scope and credentials independently.
Troubleshooting
My receiving system is not getting events
My receiving system is not getting events
Confirm the webhook is active, the target URL is reachable, and the selected event set matches the activity you are testing.
Signature verification fails
Signature verification fails
Make sure your endpoint uses the raw request body and the current signing secret when calculating the HMAC signature.
I need only one agent's events
I need only one agent's events
Edit the webhook and set the Agents field instead of leaving it empty.
Next Steps
Webhook Events Reference
Review event names, payload envelopes, headers, and retry behavior
Webhook Implementation Guide
Build a receiver that is fast, safe, and easy to debug
Integration Testing
Validate your endpoint and end-to-end event handling
Integrations
Connect other account-level integrations in the same account
Secrets
Manage reusable credentials for supported configurations