Revox

Connect AI agents to Revox, the outbound AI voice calling platform, building reusable assistants with their own prompt, voice, and retry policy. Agents place calls and read outcomes back into the flow.

1 trigger 26 actions API key available

Platform Documentation ↗ Capability data verified 2026-08-01

A CRM segment refresh produces this week's outbound list

Agent reads each record's personalisation variables and builds the campaign contact list

Agent runs Create Campaign with launch set to false, saving it as a draft rather than starting it

Agent reads back Get Campaign Rows and Get Assistant so the list and the exact prompt can be checked together

Agent runs Get Phone Number History on every destination to drop anyone already contacted

Agent posts the draft, a Preview Voice sample and the deduplicated count to the campaign owner

The owner approves the script and the audience, and the agent runs Launch Campaign

What This Integration Enables

Revox treats an AI caller as a configuration you version, not a conversation you improvise. An assistant carries the system prompt handed to the model, the opening sentence and how it is produced, the voice and its provider, closing behaviour, voicemail handling and a retry policy. A campaign carries the contact list, the caller ID, a concurrency ceiling and a schedule. Both are addressable objects with their own identifiers, which means an agent can inspect exactly what will be said and exactly who will hear it before a single call is placed.

That separation is what makes the platform automatable in a way a black-box dialer is not. FlowRunner agents create assistants per persona, place single calls with per-recipient prompt variables, save campaigns as drafts for review, launch them when a person approves, and read the four-stage funnel from numbers called through to hot leads. On Call Completed emits the finished call with transcript, recording URL and conversation outcome, filterable to the outcomes that matter, so the handoff to a human rep is native rather than bolted on. This is Orchestration as a Service applied to outbound: the calling platform does the calling, and FlowRunner decides what happens on either side of it.

Without FlowRunner

Prompts change without review The assistant's wording shifts between campaigns and nobody reads it before it runs

Duplicate outreach A prospect gets called twice because two campaigns drew from overlapping lists

Outcomes read as a dashboard Interest surfaces in a weekly report rather than in the rep's queue

With FlowRunner

Draft state used as a review step The campaign exists, unstarted, so the prompt and the list can be read before anyone is dialed

History checked before dialing Every number is tested against the organisation's full prior contact history

Interest routed as work Calls that ended Interested arrive with their transcript in the rep's channel

Use Case Scenarios

Inbound form to a live conversation in seconds

A form is submitted in Typeform or on the site. Within seconds the agent runs Place Call against the single number in E.164 form, referencing an existing assistant by identifier and substituting prompt variables so the opening sentence names the company and the thing they asked about. A concurrency key caps how many of these run at once, which matters when a campaign lands and a webinar ends at the same hour. The call order can resolve over several attempts spanning a few days, with automatic retries when voicemail is detected, so a single missed pickup does not end the follow-up.

Hot lead handoff the moment the call ends

On Call Completed is configured to fire only for calls whose conversation outcome is Interested. When it fires, the agent has the full call record: transcript, recording URL, duration and the assistant that handled it. It writes the transcript to the HubSpot record, posts to the owning rep in Slack with the two or three sentences where the prospect actually expressed interest, and creates the follow-up task. The rep opens a lead that has already been qualified by a conversation they can read in full. Get Campaign Statistics closes the loop with the funnel from numbers called through to hot leads, plus the distribution of conversations by outcome and data-extraction coverage.

An opt-out that stops the machine, with a person deciding how far it stops

Someone replies to an email asking not to be contacted, or an unsubscribe lands in the CRM. The agent runs Pause Call immediately, which is the safe move because it halts further attempts without being terminal. Then it asks a question it should not answer alone. If the opt-out came from a named contact, cancelling that one call order is obvious and the agent runs Cancel Call. If the opt-out came from a shared inbox at a large account with eleven contacts in the running campaign, the agent posts the account, the eleven contacts and their current call states to the campaign owner, because Cancel Campaign is terminal and cannot be undone by resuming. A person decides whether one contact opted out or an entire company did.

Human-in-Loop Highlight

Launch Campaign is where this connector stops, and Revox almost designs the gate for you: setting launch to false at creation saves the campaign as a draft precisely so a human can look at it. The agent's job is to make that look worth ten seconds instead of ten minutes. Before it asks, it assembles three things a reviewer would otherwise have to hunt for. Get Assistant returns the exact system prompt and opening sentence in force right now, not the one written in the brief. Get Campaign Rows returns every destination number with its own prompt variables, so a reviewer can see the personalisation as it will actually render. Preview Voice generates a short sample of the assigned voice, because reading a script and hearing it are different acts of judgment.

Then the agent posts it: "Campaign 'EMEA Q3 reactivation' is a draft, 340 rows after removing 47 numbers with prior contact history. Assistant 'Nadia, senior AE' opens with the line below. Voice sample attached, 8 seconds. Concurrency ceiling 12, caller ID +44 20 7946 0182. Launch it?" The owner reads the opening line, changes one phrase with Update Assistant, and approves. The agent runs Launch Campaign. Cancel Campaign is terminal and Pause Campaign does not un-say anything already said, so the only moment this decision can be made cleanly is before the first dial. That is the moment FlowRunner puts it in front of someone.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

26 actions

Assistants

Create Assistant Creates an AI calling assistant defining how the agent behaves on every call placed against it: the system prompt, the opening sentence and how it is produced, the voice and its provider, closing behaviour, voicemail handling and retry policy. Assistants are reusable, so one per campaign persona is the normal pattern.
List Assistants Returns every assistant with its full configuration including prompt, voice settings and opening sentence. Used to discover identifiers before placing calls or creating campaigns.
Get Assistant Returns one assistant with its complete configuration. Used to show a reviewer the exact prompt and voice in force before a launch, or to snapshot a configuration for the record.
Update Assistant Applies a partial update, so a prompt can be tweaked, a voice swapped or a retry policy adjusted without rebuilding the configuration. Changes take effect on calls placed after the update.
Delete Assistant Permanently removes an assistant. Campaigns and scheduled calls referencing it can no longer run, so flows verify nothing depends on it first.

Calls

Place Call Places an outbound call order to a single number in E.164 format, referencing an assistant by identifier or passing a one-off configuration for this call alone. Can be scheduled, resolves over several attempts spanning a few days with automatic voicemail retries, substitutes prompt variables per recipient, and accepts a concurrency key that caps parallel calls.
Get Call Returns the full record of a call order: status, every attempt made, the transcript, the recording URL, timestamps and any metadata stored when the call was placed. Polled to detect completion, or called once after a completion trigger fires.
Search Calls Returns a paginated list of call attempts filtered by assistant, campaign, assignee, direction, status, conversation outcome, who answered, caller ID and recipient number, with optional free text. This is the workhorse for reporting and for pulling completed conversations into a CRM.
Pause Call Pauses an in-flight or scheduled call order so no further attempts are made until it is resumed. Used as a circuit breaker when an upstream system says the recipient should not be contacted.
Resume Call Resumes a paused call order so Revox continues attempting it under the assistant's retry policy and calling window.
Cancel Call Cancels a call order outright. Unlike pausing this is terminal, so it is the right action once a contact has genuinely opted out.
Get Phone Number History Returns every call the organisation has made to or from a number, across all assistants and campaigns. Used to check whether a lead has already been contacted before dialing them again.

Campaigns

Create Campaign Creates a bulk outbound campaign from a contact list, each entry carrying a destination number and its own prompt variables. Launches immediately by default; setting launch to false saves it as a draft for review, which is the pattern a gated flow uses. Retry behaviour, caller ID, concurrency ceiling and a scheduled start are all set here.
List Campaigns Returns every campaign belonging to the organisation, covering drafts, running, paused and completed alike, with status and assistant assignment.
Get Campaign Returns one campaign with its status, assistant assignment, schedule and configuration. Used to confirm a draft is correct before launching it.
Update Campaign Applies a partial update: rename, swap the assistant, replace the contact list, change the caller ID, adjust the concurrency ceiling or retry policy, or move the scheduled start. Editing the contact list is normally done while the campaign is still a draft.
Launch Campaign Starts a campaign saved as a draft, moving it into the running state so Revox begins dialing under the configured schedule and concurrency ceiling. This is the operation flows hold behind an approval.
Pause Campaign Pauses a running campaign so no further calls are placed. Calls already in progress are unaffected, which makes this a safe throttle when downstream capacity runs short.
Resume Campaign Resumes a paused campaign so Revox continues through the remaining contacts under the existing schedule and retry policy.
Cancel Campaign Cancels a campaign outright so no remaining contacts are dialed. This is terminal and cannot be undone by resuming, so pause instead when the stop is temporary.
Get Campaign Statistics Returns the performance report: the four-stage funnel from numbers called through to hot leads, two secondary tiles, the distribution of conversations by outcome, the hot lead list and data-extraction coverage. Counts are over distinct numbers normalised to E.164.
Get Campaign Rows Returns every contact row loaded into a campaign with its destination number and prompt variables. Used to read a draft's list back before editing it, or to reconcile the uploaded list against the source system.

Voices

List Voices Returns every voice available for AI calls, covering the preset Cartesia, ElevenLabs and Gradium catalogues plus any voices cloned by your organisation.
Preview Voice Generates a short audio sample so a voice can be auditioned before it is assigned. Custom preview text can be supplied, and Cartesia voices additionally accept a model, speed and volume.

Account

List Phone Numbers Returns the numbers provisioned on the account, which are the caller IDs available when configuring assistants, placing calls or launching campaigns.
Get Current User Returns the user the API key authenticates as, including its organisation. Used as a connection health check and to confirm which workspace a flow is operating against.

Triggers

1 triggers

Event Triggers

On Call Completed Fires when an outbound call finishes, emitting the full call record including transcript, recording URL and conversation outcome. Monitoring can be narrowed to a single assistant or campaign and to particular outcomes, so a flow can react only to prospects the assistant marked as interested. The first poll establishes a baseline without firing, so historic calls are not replayed.

Frequently Asked Questions

What can FlowRunner do with Revox?

FlowRunner agents can run Create Assistant, List Assistants, and Get Assistant in Revox, plus 23 more actions.

Does connecting Revox to FlowRunner require OAuth?

No. Revox connects to FlowRunner with an API key, no OAuth flow required.

Can Revox trigger a FlowRunner workflow automatically?

Yes. Revox supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Revox

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us