You can connect Vapi to Currai entirely through their dashboards: create Currai’s built-in Vapi connector, copy its generated webhook URL and one-time Bearer secret, add that secret as a custom Bearer Token credential in Vapi, and assign the credential to the assistant’s Webhook Server. After publishing the assistant, complete a real call and confirm that Currai receives and analyzes it.
This connector forwards the completed-call report after a call ends. It is not a live-call relay, does not backfill earlier Vapi calls, and does not require a Vapi private API key, a Currai SDK, or capture code in your application.
As an Amazon Associate I earn from qualifying purchases.
What the Vapi–Currai connector actually does
Currai’s official connector accepts Vapi’s end-of-call-report, reconstructs the completed provider conversation as a Currai session, normalizes the call and conversation turns, and runs Currai’s existing User Story, intent, violation, alert, and analytics processing. The documented dashboard procedure is described in Currai’s Vapi connector guide and in its August 30, 2026 engineering walkthrough.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The timing matters: Currai receives the report after Vapi ends the call. The connector is therefore suitable for post-call review, quality analysis, intent reporting, and violation detection. It is not suitable for sending live audio or transcripts to Currai, handling an assistant’s live tool call, making transfer decisions, or controlling an active call.
- Included: completed Vapi calls, normalized conversation turns, Currai sessions, User Story analysis, intents, violations, alerts, and analytics.
- Not included: historical-call backfill, live-call relay, call-control requests, assistant requests, transfers, or other real-time webhook workflows.
- Credentials: the setup uses a Currai-generated Bearer secret as a Vapi custom credential; a Vapi private API key and Currai SDK are not needed for this connector route.
Currai’s connector overview explains that imports consume the normal workspace event allowance: one event for the call boundary plus one event for each normalized conversation turn. That is product metering, not a performance benchmark; the allowance can affect whether a delivery succeeds.
Read Currai’s connector overview for the broader connector model and event accounting.
What you need before starting
Have these items ready before opening either dashboard:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- A Currai workspace in which you have owner or administrator access.
- A Vapi assistant that can place or receive a complete test call.
- Permission in Vapi to create credentials and edit the assistant’s server settings.
- A way to publish the assistant after changing its configuration.
No physical hardware, special setup utility, or printed manual is required. The work is configuration in Currai and Vapi’s web interfaces.
Step 1: Create the connector in Currai
- Open the connector settings. In Currai, go to Settings → Connectors.
- Choose Vapi. Select Connect Vapi from the available connector options.
- Copy both generated values. Currai displays a webhook endpoint and a Bearer secret. Copy the complete endpoint and save the secret in a secure password manager or other protected secret store.
- Do not close the page before saving the secret. Currai stores only a hash of the connector secret and cannot display the original value again. Treat the first display as your only opportunity to copy it.
The endpoint is the destination Vapi will call when it sends the completed report. The secret is the credential Vapi will present in the Authorization header. Keep the endpoint and secret together while completing the Vapi steps, but do not paste the secret into documentation, screenshots, tickets, or client-side code.
If the secret was lost
Return to the connector settings and rotate the secret. Rotation invalidates the previous value immediately. After rotating, replace the token in Vapi’s custom credential before testing again; leaving the old value in Vapi produces an authentication failure.
Step 2: Add the Currai secret as a Vapi credential
- Open Vapi’s integration settings. Go to Integrations → Server Configuration.
- Create a custom Bearer Token credential. Choose the credential type labeled Bearer Token.
- Paste only the Currai secret. Put the one-time Currai value in the token field. Do not manually type the word
Bearerbefore it. Vapi adds the Authorization prefix when it sends the request. - Save the credential. Give it a recognizable name, such as
Currai production connector, so you can identify it when assigning the assistant’s server.
Using the credential object keeps the secret out of the assistant’s URL and lets you replace it cleanly if Currai rotates the value. A 401 response later in the process usually means that Vapi is using an outdated, incomplete, or incorrectly configured token.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Step 3: Point the Vapi assistant at Currai
- Open the assistant. In Vapi, select the assistant that will make the test call.
- Open advanced webhook settings. Go to Advanced → Webhook Server.
- Paste the complete Currai endpoint. Enter the generated Currai URL into Server URL. Do not shorten it, remove its path, or substitute a dashboard URL.
- Select the credential. Choose the custom Bearer Token credential that contains the current Currai secret.
- Limit the event selection where available. If the dashboard provides a
serverMessagesselector, select onlyend-of-call-report. Currai’s connector is designed for this completed-call payload. - Save and publish. Save the assistant, then publish the configuration. A draft change does not necessarily affect the assistant used by your test call.
Vapi applies one applicable Server URL according to its URL-priority rules. Depending on your configuration, a URL can exist at the assistant, phone-number, or account level. Replacing an existing destination can stop another integration from receiving events, so check the current setting before you overwrite it.
When another webhook already exists
If another system must continue receiving Vapi events, do not casually replace its destination. Preserve the existing integration and use a forwarding service or server route that sends the unchanged final report to Currai with Currai’s Bearer authorization. The built-in connector itself does not make Vapi deliver one event to two independent destinations; Vapi chooses one applicable Server URL.
Forward the completed report only after confirming that the forwarding layer preserves the payload, including the artifact.messages array that Currai needs for turn reconstruction. Keep the Currai secret server-side and never expose it in browser JavaScript.
Step 4: Complete an end-to-end test call
A webhook test can show that authentication works, but it cannot prove that Currai can normalize a real transcript and run its analysis. Use a published assistant and complete one genuine call.
- Start a call with the Vapi assistant.
- Exchange enough turns to create a meaningful conversation.
- End the call normally so Vapi generates its final report.
- Wait for Vapi to deliver the
end-of-call-reportto the Currai endpoint. - In Currai, open Settings → Connectors and watch the connector status change from Waiting for first call to Receiving data.
- Open Analyse → User Stories and verify that the conversation is readable rather than an empty session.
- Open Observe → Events to inspect the imported call-boundary and conversation events. Check intents and violations if those analyses are enabled in your workspace.
The first successful call is the meaningful verification point because it tests the full chain: published Vapi configuration, authentication, delivery, payload shape, transcript normalization, event accounting, and Currai analysis.
How data moves after a call
- Vapi runs the assistant and records the call artifacts.
- When the call ends, Vapi creates an
end-of-call-report. - Vapi posts that report to the one applicable Server URL, using the selected Bearer credential.
- Currai authenticates the request with the generated secret.
- Currai reconstructs the completed provider conversation as a session and normalizes its turns.
- Currai emits the corresponding call-boundary and turn events within the workspace allowance.
- Currai runs its User Story, intent, violation, alert, and analytics pipeline.
Currai’s connector documentation says that the final Vapi report must contain artifact.messages for conversation turns to appear correctly. A plain transcript without that message structure can authenticate successfully yet leave Currai with no normalized turns.
Limits you should plan for
No historical backfill
Creating the connector does not import calls that happened before the connection was configured. Only reports delivered after the published setup can enter Currai through this route. If you need older data, you would need a separate export or ingestion process; the dashboard connector does not provide a backfill switch.
Post-call rather than real-time processing
The connector receives the final report after the call. It cannot provide Currai with a live stream, answer an in-call assistant request, invoke a tool, make a transfer, or control the call while it is active. Keep real-time responsibilities in the Vapi workflow or another integration designed for call control.
Workspace event allowance
Currai counts one call-boundary event and one event for each normalized conversation turn. A long conversation therefore consumes more events than a short one. If the workspace allowance is exhausted, delivery can fail with event_limit_exceeded. Check the allowance before load testing or importing a high volume of calls.
Secret handling
Currai describes connector secrets as stored in non-readable form and says the connector does not retain recording URLs or raw phone numbers. Those are Currai’s published product statements, not an independent security audit. Apply your own access controls, rotate credentials when staff or vendors change, and restrict who can edit Vapi server settings.
Troubleshooting by symptom
Currai still says “Waiting for first call”
- Confirm that the assistant was published after the webhook change.
- Make sure the test call used that published assistant, not an older deployment or a different assistant.
- Verify that
end-of-call-reportis enabled in the assistant’s server-message selection. - Confirm that the endpoint copied into Vapi is the complete Currai-generated URL.
- End the call normally and allow time for Vapi to send the final report.
Vapi returns 401 Unauthorized
- Check that the assistant selected the custom credential containing the current Currai secret.
- Ensure that only the secret value was pasted; do not prepend
Beareryourself. - If the Currai secret was rotated, update the Vapi credential immediately because the previous value is invalid.
- Check for copied whitespace, truncation, or a token from a different Currai workspace.
The call appears, but there are no conversation turns
- Inspect the final Vapi report and confirm that
artifact.messagesis present. - Verify that your forwarding layer, if any, sends the unchanged report body rather than reducing it to a plain transcript.
- Check Observe → Events for a call-boundary event without normalized turn events.
- Run a new completed call after correcting the payload; changing the connector does not retroactively rebuild a prior failed import.
An event-limit error appears
- Look for
event_limit_exceededin the delivery or connector details. - Estimate usage as one event for the completed call plus one per normalized turn.
- Reduce test volume or increase the applicable Currai workspace allowance before retrying.
- After capacity is available, complete a new call to verify delivery.
Local testing cannot receive the webhook
Vapi cannot post directly to a private localhost address. Expose your development endpoint through an HTTPS tunnel with a public URL, then use that URL for testing. Vapi’s CLI forwarder can help route webhook traffic during development, but it is not itself a tunnel and does not create a public URL. See Vapi’s local webhook testing guidance.
Built-in connector versus custom browser-call capture
Currai documents two different Vapi integration patterns. The built-in connector is the appropriate choice when you want dashboard-only setup for completed calls. Currai’s code-based browser example is a separate pattern for teams that own a Vapi browser call and need application-controlled, server-side capture.
| Route | Best fit | What you configure | Main trade-off |
|---|---|---|---|
| Built-in Vapi connector | Import completed Vapi calls without adding capture code to the live application | Currai connector, Vapi Bearer credential, assistant Webhook Server, and published event selection | Post-call only; uses the applicable Vapi Server URL and Currai event allowance; no historical backfill |
| Custom browser-call capture | A team instrumenting an application that owns a Vapi browser call and needs server-side capture details | An application route, server-side credentials, and custom request handling | Requires application implementation and credential management |
The custom pattern is not a prerequisite for ordinary Vapi connector setup. Consult Currai’s code-based Vapi integration example only if your application needs that additional control.
Operational checklist for production
- Record which Currai workspace and Vapi assistant are connected.
- Store the one-time Currai secret in an approved secret manager.
- Document the connector endpoint without publishing the Bearer secret.
- Check whether an assistant-, phone-number-, or account-level Server URL already serves another system.
- Confirm that only
end-of-call-reportis selected when the dashboard offers event filtering. - Publish the assistant and place a complete test call before relying on production reporting.
- Verify both Analyse → User Stories and Observe → Events, not only a successful HTTP response.
- Monitor Currai’s event allowance, especially for long conversations or high call volume.
- Rotate the Currai secret when access changes and update the Vapi credential immediately after rotation.
- For local development, use an HTTPS tunnel rather than a
localhostURL.
Frequently encountered design decisions
Should you select every Vapi server message?
No. For the Currai connector workflow, select end-of-call-report where Vapi exposes individual server-message choices. Sending unrelated live or control events adds noise and can direct event types Currai’s connector is not intended to process.
Can a webhook test replace a real call?
No. A webhook test can validate reachability and authentication, but only a completed call demonstrates that Vapi produced the expected final payload and that Currai normalized its messages and ran analysis.
Do you need to expose Currai’s endpoint in client-side code?
No. Put the endpoint and credential in Vapi’s server configuration. If you build a forwarding route for an existing destination, keep the Currai Bearer secret on the server and never embed it in browser code.
Free tools Windows power users keep installed
One-click scans. No signup required.
Bottom line
The no-code path is a short, dashboard-based sequence: create Currai’s Vapi connector, save its one-time secret, add that secret as a Vapi Bearer Token credential, assign the Currai endpoint under the assistant’s Webhook Server, publish, and complete a real call. The result is reliable post-call analysis in Currai, provided you preserve any existing Vapi Server URL behavior, send the final report with artifact.messages, and budget for one call event plus one event per normalized turn.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
