Train your AI on Webhooks
When you need direct, low-latency access to Open events from your own infrastructure, webhooks deliver them to any HTTPS URL. Every call event, transcript, transfer, and outcome can be streamed in real time and processed by your own services.
Connect once, and Open automatically keeps your AI agent's knowledge up to date. When you update content in Webhooks, the changes sync automatically—no manual retraining required.
What can be synced
Call events — call.started, call.ended, call.failed.
Conversation events — transcript.ready, intent.detected, sentiment.scored.
Transfer events — transfer.requested, transfer.completed.
Outcome events — outcome.tagged, qa.scored.
Features
- •Event-typed payloads — Each event has a typed payload (call.started, call.ended, transcript.ready, transfer.requested, outcome.tagged).
- •Signed delivery — HMAC-signed payloads with replay protection so you can verify origin server-side.
- •Retries with backoff — Failed deliveries retry with exponential backoff and a configurable dead-letter queue.
- •Filter by agent — Subscribe to events from specific agents only, to keep the firehose manageable.
Requirements
- •HTTPS endpoint with TLS
- •Ability to verify HMAC signatures
How to connect
- 1.In Open, go to Settings → Integrations → Webhooks
- 2.Add an HTTPS endpoint URL
- 3.Subscribe to event types and (optionally) filter by agent
- 4.Copy the signing secret and verify HMAC signatures server-side
- 5.Test with a sample event and confirm receipt
Good to know
- Payloads include event metadata, related IDs, and links to fetch full records
- Replay events from the dashboard for development and testing
- Use the native API for two-way operations; webhooks are one-way notifications
Security: Open only requires read access to your Webhooks. We never write, modify, or delete your content. All data is encrypted in transit and at rest. GDPR compliant, working toward SOC 2 Type II.
Ready to connect Webhooks?
AI Training → Sources → Webhooks
Other training sources