How to connect Retell AI to Currai using Currai Connectors

Retell AI can run the live voice conversation. Currai can turn the completed call into product and quality signals your team can use.

The Currai Retell AI connector links the two with a signed webhook. Once it is configured, Retell sends a call_ended event after each completed voice call. Currai verifies the signature, reconstructs the conversation, creates a session and conversation-turn events, and runs the same User Story, intent, violation, alert, and analytics pipeline used for native Currai captures.

You do not need to install a Currai SDK or add capture code to the live call path.

What is Currai?

Currai is a user-intelligence and agent-quality platform for AI applications. It helps product and engineering teams understand what users are trying to accomplish, where agents fail, which policies are violated, and what evidence sits behind every signal.

For a voice call, Currai can show:

• the complete user and assistant conversation;
• the User Story behind the call;
• detected intents and recurring demand;
• violation matches and the evidence that triggered them;
• unsuccessful turns, errors, alerts, and quality trends.

Currai does not replace your voice provider. It adds a quality and product intelligence layer around the conversations the provider already handles.

What is Retell AI?

Retell AI is a platform for building and operating real-time voice agents. It manages the live voice experience and produces a call record when the conversation ends.

Retell can send that completed record to a webhook URL as a call_ended event. The event can include call metadata and a structured transcript_object with the user and agent utterances Currai needs for post-call analysis. Retell remains responsible for the live conversation; Currai receives the completed result afterward.

How the Retell AI connector works

The connector has a simple flow:

1. You create or identify the Retell API key marked with the Webhook badge.
2. You enter that key in Currai, where it is encrypted and never redisplayed.
3. Currai generates a unique Retell webhook URL for the workspace.
4. You register the URL at the Retell account or agent level.
5. Retell signs and sends a call_ended event when a call finishes.
6. Currai verifies and imports the call once, even if Retell retries delivery.

Currai creates one retell.voice_call boundary event for the completed call and one retell.conversation.turn event for each normalized user turn and its following assistant response. These events use the workspace's normal event allowance.

Before you start

You need:

• a Currai workspace where you are an owner or admin;
• a Retell AI voice agent that can complete a test call;
• access to Retell Settings → API Keys and Settings → Webhooks.

The connector imports calls completed after setup. It does not backfill older Retell calls or import chat sessions.

Step 1: Create or identify the Retell webhook key

In Retell, open Settings → API Keys. Create a dedicated key such as Currai, or select an existing key and choose Set as Webhook Key from its actions menu.

Confirm that the selected row has the blue Webhook badge. Retell uses this designated key to sign webhook deliveries.

Copy the complete key value when Retell displays it. The masked dots in the API Keys table are not the key, and Currai cannot use the masked representation.

Step 2: Generate the Retell webhook URL in Currai

In Currai, open Settings → Connectors. Find the Retell AI card and select Setup.

1. Paste the complete Retell webhook-designated API key into Webhook API key.
2. Paste the raw value without adding Bearer.
3. Select Generate webhook URL.
4. Copy the endpoint beginning with https://www.currai.app/api/connectors/v1/retell/.

Currai encrypts the Retell key and does not display it again. If the key marked Webhook changes in Retell, select Update key in Currai and enter the new value before another call ends.

Do not shorten the generated endpoint or replace its final connection ID. Each Currai workspace connection has its own URL.

Step 3: Register the Currai webhook in Retell

To connect every voice agent in the Retell workspace, open Settings → Webhooks and paste the complete generated Currai endpoint into the account-level URL field.

Save the change, then select Test to confirm Retell can reach and authenticate with Currai.

If you only want to connect selected agents, configure the generated URL as an agent-level webhook instead. An agent-level URL overrides the account-level URL for that agent.

Where Retell offers event filtering, select only call_ended. Currai safely acknowledges other authenticated Retell event types without importing them.

Step 4: Complete a real test call

Start and finish a call with a connected Retell voice agent. Exchange at least one user and agent turn so the completed record contains a structured conversation.

Return to Currai → Settings → Connectors. The Retell AI card should move from Waiting for first call to Receiving data after Currai verifies and imports the signed event.

The Retell Test action can confirm delivery and authentication, but a real completed call is the best acceptance test because the test request may not contain a usable call_ended transcript.

Step 5: Verify the imported conversation

After the call is imported, check:

• Analyse → User Stories for the readable conversation and derived need;
• Observe → Events for retell.voice_call and retell.conversation.turn;
• Analyse → Intents for matched user demand;
• Analyse → Violations for rule matches and supporting evidence;
• Alerts and analytics for any signals produced by the normal capture pipeline.

Currai maps Retell's agent transcript role to assistant, coalesces consecutive utterances from the same role, and preserves the normalized conversation on the call boundary. An unanswered final user turn is marked unsuccessful. Repeated webhook deliveries do not create another session or consume duplicate event credits.

Calls that never connect or end before speech can still create a call-boundary event without conversation-turn events.

Account-level and agent-level webhooks

Use the account-level webhook when every Retell agent should send completed calls to the same Currai workspace. Use an agent-level webhook when only selected agents belong in that workspace.

If an agent already points to another webhook server, replacing its URL can interrupt the existing integration. Keep the current endpoint and forward the signed request to Currai, or dedicate the Currai endpoint to a different agent. Currai is a post-call analytics destination, not a relay for live call control or tool requests.

Local development with ngrok

Retell cannot deliver a webhook to localhost. To test a local Currai instance, expose it through an HTTPS tunnel such as ngrok and register the complete generated development endpoint in Retell.

For the deployed connector, switch back to the generated https://www.currai.app endpoint. Temporary ngrok addresses should not be used for production delivery.

Usage and privacy

Each imported call consumes one Currai event for the call boundary plus one event per normalized conversation turn. If the workspace reaches its event limit, the connector reports event_limit_exceeded instead of importing unlimited calls.

Currai does not persist raw Retell API credentials, caller phone numbers, recording or log URLs, access tokens, dynamic-variable collections, or word timing arrays in the imported call. The connector uses a pseudonymous user ID, and previously imported Currai data remains available if the connection is disabled.

Troubleshooting

Currai still says “Waiting for first call”

Complete a real call and confirm that the account or agent webhook contains the entire generated Currai URL. If you configured an account-level webhook, check whether the agent has its own URL overriding it.

Retell or Currai reports an authentication error

Confirm that Currai stores the complete key currently marked Webhook in Retell. If the designation or key changed, use Update key in Currai before testing again.

The Retell test succeeds but no conversation appears

The test action verifies webhook delivery; it may not include a completed call or structured transcript. Finish a real voice call and wait for its call_ended event.

The call appears without conversation turns

Confirm that the completed Retell call contains textual entries in transcript_object. Calls that never connected or ended before speech can legitimately have no turn events.

Currai shows a delivery error

Open the connector card and read the safe error message. Currai retries transient processing failures automatically. An event_limit_exceeded error means the workspace needs additional event capacity before another call can be imported.

What to do next

Once the first call appears, configure the Currai signals that matter to your team:

• create intents for the caller requests you want to measure;
• create violation rules for behavior the agent must avoid;
• review User Stories to find recurring needs and friction;
• configure alerts for important failures or policy breaches.

For the shorter product reference, see the Retell AI connector setup guide and Connectors overview. For provider behavior, see Retell's official webhook setup, webhook overview, and API key management documentation.