Webhook events for call outcomes

Send structured call outcomes to CRMs, calendars, ticketing tools, sheets, Slack, Teams, or internal systems without turning the project into a custom voice stack.

Map webhook destination See webhook integration

Technical example

Webhook delivery

POST /havio/events
X-Havio-Event: call.completed
X-Havio-Signature: sha256=...
Idempotency-Key: call_01JLC8W9Q4P2N7A6K3_completed

{
  "callId": "call_01JLC8W9Q4P2N7A6K3",
  "event": "call.completed",
  "outcome": "booked",
  "destination": "google_calendar",
  "retryCount": 0,
  "destinationStatus": "delivered"
}

Best buyer

Teams that want automation without a full custom integration

Primary risk

No owner for failed webhook deliveries

Havio advantage

Structured outcomes and clear retry ownership

What to send

A webhook should carry the minimum useful outcome, not a noisy transcript dump by default.

Caller, intent, urgency, and language
Summary, tags, and next action
Destination status and failed-write reason

How to verify delivery

Webhook buyers need to know if a call outcome landed in the right place.

Delivery timestamp and response code
Retry attempts and final status
Alert for unresolved writes

Security expectations

Treat webhook destinations as production systems that may receive customer or caller data.

HTTPS endpoint
Signature verification
Least-privilege destination token and retention review

Delivery contract

Webhook delivery should be explicit enough that operations can audit the result after every handled call.

Stable event names and schema version
Idempotency key tied to the call outcome
Retry window, final failure state, and replay owner

Operational fallback

A webhook is not complete until the team can see what happened when delivery fails.

Visible failed-delivery state in the call summary
Human alert when retries exhaust
Replay process that does not duplicate CRM, calendar, or ticket records

Related developer paths

Keep the workflow contract connected.

Technical pages work best when they point back to the operational buyer questions: source of truth, fallback, billing, security, and review.

Developer docs Slack alerts Microsoft Teams alerts

POST /havio/events X-Havio-Event: call.completed X-Havio-Signature: sha256=... Idempotency-Key: call_01JLC8W9Q4P2N7A6K3_completed { "callId": "call_01JLC8W9Q4P2N7A6K3", "event": "call.completed", "outcome": "booked", "destination": "google_calendar", "retryCount": 0, "destinationStatus": "delivered" }