The Read.ai connector is currently in beta. OAuth is the primary connection method, with a bearer-token fallback while OAuth rolls out fully.
Connecting Read.ai
1
Open integrations settings
In CallVault, go to Settings → Integrations → Read.ai.
2
Connect with OAuth
Click Connect and authorize CallVault from your Read.ai account. If OAuth isn’t available for your account yet, you can paste a Read.ai bearer token instead.
3
Choose your import settings
Decide whether to import your existing Read.ai meeting library or only sync new meetings going forward.
4
(Optional) Set up the webhook
For real-time sync, create a webhook in Read.ai’s Integrations settings using the URL CallVault provides, then paste the signing key Read.ai generates back into CallVault. Send a test request to verify.
What syncs
For each imported Read.ai meeting:- Transcript
- Meeting title
- Date and duration
- Attendees — from Read.ai’s calendar invitee data, when available
meeting_end events), or on your next manual sync otherwise.
Where synced calls land
New calls from Read.ai land in your My Calls workspace by default. Use Routing Rules to route them automatically.Managing the connection
Go to Settings → Integrations → Read.ai to check connection status or disconnect. Disconnecting stops future syncs but does not delete calls already imported.Troubleshooting
OAuth isn't available for my account
OAuth isn't available for my account
While Read.ai is in beta, paste a Read.ai bearer token instead of using OAuth — the option is on the same connection screen.
New Read.ai meetings aren't syncing
New Read.ai meetings aren't syncing
Check that the webhook signing key matches what Read.ai generated, and that the last test request came back verified in Settings → Integrations → Read.ai.
A meeting is missing attendee names
A meeting is missing attendee names
Attendee data depends on what Read.ai’s calendar invitee list includes for that meeting — CallVault imports whatever Read.ai provides.

