Setup Guide
Configure Ringover webhooks to automatically send call recordings and metadata to Coldread for AI transcription and analysis. Takes about 10 minutes.
If you haven't already, create a Coldread account and navigate to Settings → Integrations in your dashboard.
Click "Add Integration" and select Ringover as your provider. Coldread will generate a unique webhook URL and an optional webhook secret for signature verification.
Your Coldread webhook URL follows this format:
https://coldread.ai/api/webhooks/ringover/YOUR_INTEGRATION_IDCopy this URL from your Coldread integration settings page. You'll paste it into Ringover in the next step.
Log in to your Ringover Dashboard and navigate to:
If Ringover asks for a webhook secret or signing key, enter the secret shown in your Coldread integration settings. This ensures webhook payloads are verified.
In the Ringover webhook configuration, enable the following event types:
CALL_ENDED / call.ended
Triggered when a call finishes (required)
CALL_RINGING / call.ringing
Triggered when an incoming call rings (optional)
VOICEMAIL / voicemail
Triggered when a voicemail is left (optional)
Important: At minimum, you must enable the CALL_ENDED event. Coldread processes calls when they end and a recording is available. Without this event, no calls will be captured.
Save your webhook configuration in Ringover. To verify the connection:
You can also verify the webhook endpoint is reachable by visiting your webhook URL in a browser. You should see a JSON response with {"status":"ok"}.
If you need to forward incoming Ringover webhooks to another system (like n8n, Zapier, or custom automation), Coldread can relay the raw webhook payload after processing.
Coldread will automatically relay every incoming webhook to your specified URL using POST requests with:
X-Idempotency-Key header (prevents duplicate processing)Coldread verifies incoming Ringover webhooks using the x-ringover-signature or x-signature header. If you configured a webhook secret in both Ringover and Coldread, payloads are verified using HMAC-SHA256 before processing. This prevents unauthorized requests from being accepted.
If you did not set a webhook secret, signature verification is skipped. We strongly recommend enabling it for production use to ensure webhook authenticity.
If calls aren't showing up in your dashboard within 30 seconds:
{"status":"ok"}If Ringover reports webhook delivery failures with 401 errors:
If calls show in the dashboard but transcription is missing:
If you configured a relay URL but your external system isn't receiving webhooks:
X-Idempotency-Key headerStill having issues? Email us at support@coldread.ai with your integration ID and we'll help troubleshoot.
Having trouble connecting Ringover? Start a free trial and our team will help you get set up.