VOYP

Place outbound phone calls with a VOYP AI voice assistant by supplying a number and the context of the call. Agents make the routine call and return a tracking reference and the outcome.

7 actions API key available

VOYP website ↗ Platform Documentation ↗ Capability data verified 2026-08-01

A task reaches the point where only a phone call will settle it

Agent resolves the target with Search Places from a free-text query and a location

Agent confirms the right branch with Get Place Details, checking the address against the one on file

Agent confirms the account and its credits with Get Profile before committing to a call

The requester receives the resolved venue, its number, and the exact call context the assistant will speak from

The requester approves the number and the wording, and only then does the agent call Start Call

What This Integration Enables

Every other telephony connector in this catalog manages a phone system. VOYP makes a phone call. You give it a number and the context of the conversation, and its assistant dials, speaks, and returns a tracking URL. That is a genuinely different proposition, and it deserves a genuinely different posture: the person on the other end did not agree to talk to software, and whatever the assistant says on your behalf is said in your name.

That is why the interesting part of this connector is the lookup layer, not the calling layer. Search Places resolves a venue from a free-text query and a location, Get Place Details confirms which branch you actually mean, and Look Up Place By Phone Number runs the reverse. An agent uses those to build a proposal a person can check in five seconds. FlowRunner exists to sit above that moment: Orchestration as a Service means the agent does the finding, the drafting and the tracking, and a human owns the sentence that a stranger will hear. VOYP also publishes no webhook registration and no call-listing endpoint, so this connector has no triggers. A live call is followed through the tracking URL returned by Start Call, not by waiting for an event.

Without FlowRunner

The call sits in a queue Routine confirmations wait until somebody has a free ten minutes to make them

Wrong branch, wrong call A name-only lookup can land on the franchise across town, and nobody finds out until the booking is wrong

No record of what was said The outcome of a confirmation call lives in one person's recollection

With FlowRunner

The call happens on schedule The routine call is placed at the right time, without a person having to hold the task

The target is confirmed first The venue is resolved and checked against the record before a number is dialed

The call is traceable Each call returns an ID and a tracking URL that a flow can attach to the originating record

Use Case Scenarios

Confirming a booking that a system cannot confirm

An operations flow needs to confirm a reservation with a venue that takes bookings by phone and nothing else. The agent runs Search Places for the venue name and city, confirms the address with Get Place Details against the address on the booking record, and drafts the call context: who is calling, the reservation name, the date and party size, and the one question that needs answering. After approval it calls Start Call, stores the returned call ID and tracking URL on the booking record, and posts the tracking URL to the channel in Slack so anyone can follow the call while it is live.

Reverse lookup before a callback

An unrecognized number appears on a record and someone needs to know who it belongs to before returning the call. The agent runs Look Up Place By Phone Number, which returns the name and address of the business behind it. In most cases that answers the question outright and no call is placed at all, which is the cheapest possible outcome. Where the record is genuinely worth a call, the same lookup gives the requester the context to decide.

A running call that can be ended

A call is placed and the flow keeps the call ID. If a downstream signal makes the call unnecessary while it is still in progress, for instance the vendor answers the same question by email, the agent calls Hang Up Call rather than letting the conversation run on. Get Call retrieves the details of a single call by ID afterwards. VOYP does not publish a response schema for that endpoint, so the connector returns the response body unchanged and a flow should treat its shape as something to inspect rather than something to depend on.

Human-in-Loop Highlight

Start Call is the only action here that reaches a person, and it reaches them completely. It places a real call, consumes VOYP credits, and has the assistant carry out the supplied context in conversation with whoever picks up. Nothing about that can be taken back: not the credits, not the wrong branch, and not the wording. So the agent stops before it, every time, with the whole proposal in one message: "Resolved 'Trattoria Il Ponte' to 12 Via Garibaldi, Bologna, +39 051 555 0198. This matches the address on booking BK-4417. The assistant will say: confirming the Thursday 8pm reservation for six under the name Whitfield, and asking whether the terrace is available. Place this call?" The requester sees the exact branch and the exact words before either becomes real. If the address does not match the booking, they say so and the agent runs the lookup again rather than calling the wrong restaurant. The agent handles the search, the drafting and the tracking. A human owns the sentence.

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

7 actions

Calls

Start Call Place an outbound call to a given number and have the VOYP assistant carry out the supplied context during the conversation. Returns the call ID and a URL where the call's progress can be tracked. Calls consume VOYP credits and reach a real person, so this action belongs behind an approval.
Hang Up Call End an in-progress call by its ID, using the ID returned by Start Call. Used to stop a call that a downstream signal has made unnecessary.
Get Call Retrieve the details of a single call by its ID. VOYP publishes no response schema for this endpoint, so the response body is returned unchanged and a flow should inspect rather than assume its shape.

Places

Search Places Search for places in a given location from a single free-text query, so a phone number can be found before a call is placed. The response body is returned unchanged, as VOYP publishes no schema for it.
Get Place Details Look up the details of one named place in a given location. Used to confirm which branch a name resolves to before dialing.
Look Up Place By Phone Number Find the name and address of a place from its phone number, the reverse of Search Places. Used to identify an unknown number on a record, often removing the need for a call entirely.

Account

Get Profile Retrieve the profile of the VOYP account the API key belongs to. Used to confirm the key is valid and the account is in good standing before a flow commits to placing calls.

Frequently Asked Questions

What can FlowRunner do with VOYP?

FlowRunner agents can run Start Call, Hang Up Call, and Get Call in VOYP, plus 4 more actions.

Does connecting VOYP to FlowRunner require OAuth?

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

Can VOYP trigger a FlowRunner workflow automatically?

VOYP doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with VOYP

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

Start Building Free Talk to us