Building a voice AI agent is only the beginning. Once customers start using it, you need to understand what they are asking, where conversations fail, and whether the assistant follows your product and compliance rules.
The Currai Vapi Connector sends completed Vapi calls to Currai through an authenticated webhook. You do not need to install a Currai SDK, modify your live call flow, or share your Vapi private API key.
After each completed call, Currai can turn the conversation into:
- A readable User Story
- Detected user intents
- Quality and policy violations
- Unsuccessful conversation turns
- Call-level events and supporting evidence
- Trends and alerts across multiple calls
This guide walks through the complete connection process and explains how to verify that real calls are reaching Currai correctly.
How the Vapi connector works
Vapi continues to operate the live voice assistant. It manages the call, transcription, model execution, speech generation, and provider operations.
When a call ends, Vapi sends an authenticated end-of-call-report to a unique webhook endpoint generated by Currai.
The connection follows this flow:
- Currai generates a webhook URL and a one-time Bearer secret.
- You save the secret as a custom credential in Vapi.
- You add the Currai webhook URL to your Vapi assistant.
- Vapi sends an
end-of-call-reportwhen a call finishes. - Currai validates the report and reconstructs the conversation.
- Currai analyzes the call for user needs, failures, intents, and violations.
The connector begins importing calls completed after setup. It does not automatically import historical Vapi calls.
What you need
Before starting, confirm that you have:
- A Currai workspace
- Owner or administrator access to the workspace
- A Vapi account
- A Vapi assistant that can complete a test call
- Permission to edit the assistant's Server URL and credentials
Keep the Currai and Vapi dashboards open during setup.
Step 1: Create the connection in Currai
Sign in to Currai and open:
Settings → Connectors
Find the Vapi connector and select Connect Vapi.
Currai generates:
- A unique webhook endpoint
- A one-time Bearer secret
The endpoint begins with:
https://www.currai.app/api/connectors/v1/vapi/
Copy both values before closing the setup window.
Protect the Bearer secret
The secret authenticates webhook requests coming from Vapi. Treat it like a password.
Currai stores only a hash of the secret and cannot display the original value again. If you lose it, use Rotate secret and update the corresponding credential in Vapi.
Rotating the secret invalidates the previous value immediately.
Step 2: Create a Bearer Token credential in Vapi
Open the Vapi dashboard and navigate to:
Integrations → Server Configuration
Create a custom credential with these settings:
| Setting | Value |
|---|---|
| Authentication type | Bearer Token |
| Name | Currai |
| Header | Authorization |
| Token | The secret generated by Currai |
| Include Bearer Prefix | Enabled |
Paste only the secret value. Do not add Bearer before it because Vapi adds the prefix automatically.
The outgoing header will follow this format:
Authorization: Bearer YOUR_CURRAI_SECRET
This value is generated by Currai. It is not a Vapi public or private API key.
Step 3: Add the webhook to your Vapi assistant
Open the Vapi assistant you want to monitor and navigate to:
Advanced → Webhook Server
Complete the following steps:
- Paste the complete Currai endpoint into Server URL.
- Select the
CurraiBearer Token credential under authorization. - Set
serverMessagesto onlyend-of-call-reportwhen event selection is available. - Save the configuration.
- Publish the assistant.
Do not shorten the webhook endpoint or remove its final connection identifier. Every Currai connection has a unique URL.
Currai is a post-call analytics destination. Do not configure it as a live relay for tool calls, transfers, assistant requests, or call-control events.
Step 4: Complete a real test call
After publishing the assistant, make and complete one real call.
Use a request that produces a clear user and assistant exchange, such as:
I need to change the delivery address for an order I placed today.
Wait for the assistant to respond, then end the call normally.
A webhook test in Vapi may confirm that authentication works, but it does not prove that Currai can reconstruct a complete conversation. A finished call is required for end-to-end verification.
Step 5: Verify the connection in Currai
Return to:
Currai → Settings → Connectors
The Vapi connector should move from Waiting for first call to Receiving data.
Review the conversation
Open Analyse → User Stories and confirm that the caller and assistant messages appear as a readable conversation.
Inspect call events
Open Observe → Events and look for the call-boundary event and normalized conversation turns created from the final Vapi report.
Review detected intents
Open Analyse → Intents to see recurring user requests, goals, and problems found across conversations.
Review violations
Open Analyse → Violations to find assistant responses that conflict with the behavioral, product, or compliance rules you define.
What Currai imports
For each completed Vapi call, Currai creates:
- One deterministic session for the complete call
- One call-boundary event
- One normalized event for each conversation turn
- Product and quality signals generated from the conversation
If the final user message does not receive an assistant response, Currai can mark that turn as unsuccessful.
Vapi may retry a webhook when delivery times out or fails. Currai uses stable identities so repeated delivery does not create duplicate sessions or consume duplicate event credits.
If Vapi already sends webhooks to your server
Vapi applies Server URL priority rules and sends an event to the applicable destination.
If your assistant, phone number, or account already sends reports to your backend, replacing that URL could interrupt the existing integration.
In that situation:
- Keep your existing Vapi Server URL.
- Receive the
end-of-call-reportin your application. - Forward the unchanged report to the Currai webhook endpoint.
- Add the Currai Bearer authorization to the forwarded request.
This allows your current workflow to continue while Currai receives completed calls for analysis.
Local development
Vapi cannot send webhooks directly to localhost.
To test a locally running application, expose it through a secure HTTPS tunnel such as ngrok and use the complete development endpoint.
For production, use the generated endpoint under:
https://www.currai.app
Temporary tunnel URLs should not be used for production delivery.
Troubleshooting
401 Unauthorized
Confirm that the assistant uses the credential containing the current Currai secret.
If you rotated the secret, the old value stopped working immediately. Replace it in the Vapi credential.
The connector remains on “Waiting for first call”
Check that:
- The assistant was published after configuration
- The call was completed normally
-
end-of-call-reportis enabled - The correct Server URL is attached
- The Currai authorization credential is selected
Currai receives the call but shows no conversation
Confirm that the final Vapi report includes structured messages in artifact.messages. A plain transcript may not contain enough information to reliably reconstruct the user and assistant turns.
Delivery error
Open the connector card in Currai and inspect the displayed error.
An event_limit_exceeded error means the workspace has no remaining event allowance for additional calls.
Usage and privacy
Each imported call uses:
- One event for the call boundary
- One event for every normalized conversation turn
Connector traffic follows the workspace's normal event allowance.
Currai stores the connector secret as a hash rather than readable text. The connector is also designed to avoid retaining raw caller phone numbers and recording URLs.
Your team should still ensure that voice data collection follows your consent, privacy, and retention policies.
What to do after connecting Vapi
Once calls are arriving, use Currai to:
- Discover why customers contact your voice assistant
- Identify recurring user frustration
- Detect prohibited or unsupported assistant claims
- Monitor unsuccessful and abandoned turns
- Create alerts for important failures
- Compare quality across assistants
- Find evidence for prompt, tool, and workflow improvements
Instead of manually listening to calls or reviewing random transcripts, your team receives organized product and quality signals backed by real conversation evidence.
Start monitoring your Vapi assistant
The Currai Vapi Connector helps you analyze completed voice conversations without installing another SDK or changing the live call experience.
Vapi continues to operate the assistant. Currai helps you understand how that assistant performs with real users.
Top comments (0)