Ringg AI

The Ringg AI connector imports terminal call outcomes through call_completed. You do not need a Ringg API key. Currai generates the endpoint and Bearer secret that Ringg sends with each webhook request.

Before you start

You need:

• a Currai workspace where you are an owner or admin;
• a Ringg AI agent that can complete a real test call;
• permission to edit the agent's webhook event subscriptions.

1. Create the Currai connection

In Currai, open Settings → Connectors. On the Ringg AI card, select Connect Ringg AI.

Currai displays:

• a webhook endpoint beginning with https://www.currai.app/api/connectors/v1/ringg/;
• a one-time Bearer secret.

Copy and save the secret immediately. Currai stores only its hash and cannot display it again. If it is lost, use Rotate secret and update every Ringg agent using the previous value.

2. Configure the Ringg webhook

Open the Ringg agent's webhook subscriptions:

1. Paste the Currai endpoint into the callback URL.
2. Set the method to POST.
3. Add a header named Authorization.
4. Set its value to Bearer YOUR_CURRAI_SECRET, replacing the placeholder with the one-time secret.
5. Under Select Events, enable Call Completed only.
6. Save or publish the agent.

Do not select recording, platform-analysis, client-analysis, or all-processing events. Currai runs its own analysis pipeline and only needs Ringg's completed-call transcript.

Ringg may emit call_completed with status: "retry" while another dialing attempt is pending. Currai acknowledges that delivery without importing it, then imports the eventual terminal completed, failed, error, cancelled, or forwarded result.

3. Complete a test call

Finish one real call with the configured agent. Return to Settings → Connectors. The Ringg AI status should change from Waiting for first call to Receiving data.

Verify the result in:

• Analyse → User Stories for the readable conversation;
• Observe → Events for ringg.voice_call and ringg.conversation.turn;
• Analyse → Intents and Analyse → Violations for matched signals.

Only terminal calls delivered after the webhook is configured are imported. The connector does not backfill Ringg history.

Existing Call Completed subscriptions

Ringg supports one subscription per event type on an agent. If call_completed already points to another service, keep that callback and have the existing service forward the unchanged JSON request to Currai with the generated Authorization: Bearer … header.

Do not forward recording_completed, analysis, or all_processing_completed events to this endpoint.

Privacy and usage

Currai hashes the customer phone number before storage. It does not retain raw phone numbers, recording URLs, custom arguments, tool-call logs, Ringg analysis objects, or the complete provider payload.

Each imported terminal call uses one event for the call boundary plus one event per normalized conversation turn. Failed calls with no transcript still create a failed call-boundary event so they can appear in operational analysis.

Local development

Ringg cannot post to localhost. Expose the local Currai application with an HTTPS tunnel such as ngrok, then register the complete generated development endpoint. Use the production https://www.currai.app endpoint when testing the deployed connector.

Troubleshooting

• 401 Unauthorized — confirm the header is named Authorization and begins with Bearer followed by the current Currai secret.
• 422 Invalid Ringg call-completed report — confirm the body has event_type, a terminal status, call_id, and an array-valued transcript when a transcript is present.
• Waiting for first call — publish the agent, finish a real call, and confirm Select Events contains Call Completed.
• No conversation turns — confirm Ringg included its structured bot/user transcript array.
• Delivery error — event_limit_exceeded means the workspace has exhausted its monthly event allowance; transient capture failures are retried by Currai.

For provider behavior, see Ringg AI's official webhook setup, payload reference, and retry behavior.