Ringover
Query calls, contacts, users, groups, numbers, SMS conversations and tags, place callbacks and send SMS, through the Ringover cloud telephony public API.
About
Ringover ships in the w6w first-party pack. It declares 30 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.ringover- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication · Customer Relationship Management
Overview
Ringover is a cloud telephony and business communications platform: phone numbers, call routing, SMS and a shared contact book for sales and support teams. This app connects a workflow to its public API with an API key, on either the Europe or the United States host.
A workflow can list and search terminated calls (by date range, call type, tags, stars, users, groups, IVRs or contacts), read one call’s log entries, see the calls in progress right now, and read a call’s transcription. It can place a callback (Ringover rings your user first, then dials the recipient), send an SMS, and opt a number out of or back in to SMS. It can list and read conversations and their messages, manage the contact book (list, search, create, update, delete, add and remove phone numbers), and read the team, its users and their presence, call groups, phone numbers, call tags and the team blacklist.
Ringover answers a list with an empty 204 when nothing matches; this app returns an empty list instead, and unwraps each response into named lists with counts. Health checks verify the API key and whether the API answers.
Build with Ringover
Three routes to the same 30 actions. The Workflow tab is generated from Ringover's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Blacklisted Numbers
blacklist-list List the numbers on the team-wide blacklist. Needs Numbers Read on the key.
Get Call
call-get Fetch the log entries of one terminated call by call ID. A forwarded, transferred or IVR-routed call has several entries.
List Calls
call-list List terminated calls, newest first. Defaults to the last 15 days, 100 results; page with Offset (max 9000) or the Last ID cursor.
List Live Calls
call-live-list Snapshot of the calls in progress right now (ringing, answered, on hold). Standard users see only their own; Monitoring widens it to the team.
Search Calls
call-search List terminated calls with advanced filters: scope (direct, IVR or advanced users/groups/IVRs/numbers), call types, stars, contacts, tags and outcome flags.
Place Callback
callback-create Ring one of your users first and, when they pick up, dial the recipient. Adds call-redirection fees.
Create Contact
contact-create Create a contact in the key owner's address book, with optional phone numbers.
List Contacts
contact-list List your contacts (yours and those shared with you), optionally searching by first name, last name, company or phone number.
Update Contact
contact-update Update a contact. Ringover requires first name, last name, company and the shared flag on every update; phone numbers, if given, REPLACE the existing ones.
Get Conversation
conversation-get Fetch one conversation: members, tags, unread count and the last message.
List Conversations
conversation-list List SMS and chat conversations (first 100 by default). Without Monitoring on the key only your own are returned.
List Groups
group-list List call (ring) groups. Without Monitoring on the key only the groups the key owner belongs to are returned.
List Conversation Messages
message-list List the messages of one conversation (first 100 by default); page with the Last ID cursor.
List Numbers
number-list List the team phone numbers by assignment. Defaults to unassigned (available) numbers; the other filters need Monitoring on the key.
Opt Back In to SMS
sms-opt-in Remove a number from the team's outbound SMS opt-out list so SMS can be sent to it again.
Opt Out of SMS
sms-opt-out Add a number to the team's outbound SMS opt-out list. Later SMS to it are blocked and not charged.
Send SMS
sms-send Send an SMS from one of the team's SMS-capable numbers. Needs Conversations Write on the key; consumes SMS credit.
Get Team
team-get Fetch the team: its name, users, phone numbers, IVRs, conferences, tags and groups (the full object needs Monitoring on the key).
Get Call Transcription
transcription-get Fetch the transcription of one call (speeches per channel, status). Needs the transcription feature on the team plan.
List Users
user-list List the team users with their phone numbers and plan. Without Monitoring on the key only the key owner is returned.
Get User Presence
user-presence-get Whether a user is available, on a call, snoozed or offline, with snooze details and connected devices.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Ringover's real ids.
{
"manifestVersion": "2",
"name": "ringover-example",
"steps": [
{
"id": "call-get",
"uses": {
"app": "io.w6w.ringover",
"action": "call-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"callId": "<callId>"
}
}
]
}Here are some of the things you can do
-
Get Call
readcall-get -
List Blacklisted Numbers
readblacklist-list -
List Calls
readcall-list -
List Live Calls
readcall-live-list -
Search Calls
readcall-search
+25 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Ringover, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Ringover. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "call-get",
payload: {
callId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action call-get --payload '{"callId":"<value>"}'Give an AI agent Ringover — without giving it Ringover's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.ringover#call-get",
"input": {
"callId": "<callId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Ringover connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Ringover's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Ringover itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Ringover declares its own checks, so its health is a property of the app rather than something the host guesses at.
Ringover platform status
API reachability
Unauthenticated GET of /teams on the connection's region host. Ringover's documented 401 `{error}` answer is the expected healthy response; key validity is the `auth:api-key` check's job.