Voxloud

Manage the shared phonebook, read call records, and place click-to-call calls on the Voxloud cloud phone system. Agents connect a person to a caller straight from the record.

1 trigger 16 actions API key available

Voxloud website ↗ Platform Documentation ↗ Capability data verified 2026-08-02

On Call Event fires with Phone Call Completed on the PBX

Agent reads duration, ring time, direction, outcome, recording URL, transcription, summary and sentiment score from the event

Agent resolves the outside number against the shared phonebook with List Contacts

Agent writes the call, its summary and its sentiment against the matching CRM record

The owning rep receives the recording link and the sentiment score in their channel

When no contact matched, the rep confirms who the number belongs to before the agent calls Create Contact

What This Integration Enables

Voxloud is a cloud phone system whose most valuable asset is not the calling, it is the shared phonebook. A contact created there resolves to a name on every extension and every app on the account, and it can carry a deep link back to the originating CRM record so a rep can jump from a ringing phone to the deal in one click. Teams that treat the phonebook as a synchronized projection of the CRM get a different phone system from teams that treat it as a place people occasionally add numbers.

The call side is unusually rich for a PBX. Completed-call events deliver duration, ring time, direction, outcome, recording URL, and Voxloud's own transcription, summary and sentiment score, which means an agent can write a meaningful record of a conversation without a transcription step of its own. FlowRunner's connectors are built and verified against each vendor's official API, and the shape of this one rewards a specific discipline: read events in real time, keep the directory current, and treat every phonebook deletion as a decision rather than a cleanup step.

Without FlowRunner

Unknown numbers on the display Inbound calls arrive as digits, and whoever answers starts by asking who is calling

Call outcomes logged from memory The rep writes up the call afterwards, if there is time before the next one

Transfers fragment the record A call that moves between people leaves several partial records and no single history

With FlowRunner

The display carries a name The phonebook is fed from the CRM, so inbound calls resolve to a person and a company

The record writes itself Duration, outcome, recording, transcription and sentiment land on the CRM record without a rep typing

One call, one history Every event belonging to a call ID is pulled together into the full path the conversation took

Use Case Scenarios

Completed calls become CRM activity, with sentiment

On Call Event fires on Phone Call Completed. The agent reads the event, resolves the outside number with List Contacts, and writes an activity onto the matching record with the duration, the outcome, the recording URL and Voxloud's transcription, summary and sentiment score. Calls that scored poorly on sentiment get posted to the team channel in Slack with the recording link attached, so a manager can listen to the ones worth listening to instead of sampling at random.

The phonebook stays in step with the CRM

When a contact is created in HubSpot, the agent calls Create Contact on Voxloud with the name, the numbers in E.164 format, the company, and a CRM deep link. From the next inbound call onward, that number resolves to a name across the whole account. A nightly reconciliation compares both directions and reports the differences rather than silently resolving them, because the CRM and the phonebook disagree for good reasons often enough to be worth a look.

Call reporting that survives transfers

A nightly flow calls List Telephony Events for the previous day, narrowed to one number or the whole account, and writes each record into Google Sheets for a call report. Where a call was answered, transferred and then forwarded, it produced several records, so the agent uses Find Telephony Events By Call on the call ID to reconstruct the full path before reporting it as one conversation. The report counts conversations, not fragments.

Human-in-Loop Highlight

The irreversible operation on this connector is Delete Contact, and it is more consequential than it looks. Removing a phonebook entry does not just tidy a list, it removes the name from every extension and every app on the account, so the next time that number calls, whoever picks up sees digits. A CRM-driven cleanup will find candidates constantly: a contact whose CRM record was archived, two entries pointing at the same mobile with different spellings, an old number for a customer who moved companies. So the agent gathers rather than deletes. It reads both entries with Get Contact, checks recent call history against each number with List Telephony Events, and puts the case to the directory owner: "Two phonebook entries share +39 02 5555 0134. 'M. Bianchi, Acme Srl' has 14 calls in the last 90 days. 'Marco B.' has none and no CRM link. Delete the second, or merge the CRM link into it first?" The owner answers in one message. The agent then deletes exactly one record, and the name on the display stays correct.

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

16 actions

Account

Validate Credentials Verify that the configured API key is accepted and return the company name and administrator email tied to it. Used as a lightweight connection test, and to confirm which account a flow is pointed at before it writes anything.

Users

List Users Retrieve every user on the PBX with their extension number, currently selected outbound caller ID, and the full list of outbound numbers available to them. Used to resolve an agent name to an extension before a click-to-call, or to audit caller ID assignment.

Contacts

Create Contact Add a contact to the shared phonebook so inbound calls from that number resolve to a name across the PBX and apps. Requires a first name and a primary number in E.164 format, and can carry extra phones, emails, company details and a CRM deep link so a rep can jump straight to the originating record.
Update Contact Replace the stored details of an existing phonebook contact. Only supplied fields are sent, so this can correct a number, attach a CRM deep link, or enrich a contact an earlier flow created.
List Contacts Search the phonebook and return matching contacts with their phones, emails and CRM links. Filters are case-insensitive substring matches, so a partial number or name is enough. Used to resolve an inbound number to a person.
Get Contact Retrieve a single contact by ID with all stored phones, emails, company details and CRM linkage. Used to enrich a call event with full detail once an ID is known.
Delete Contact Permanently remove a contact from the phonebook. Calls from that number stop resolving to a name across the account, and this cannot be undone, so it belongs behind a confirmation rather than inside an automatic cleanup rule.

Calls

List Telephony Events Retrieve call detail records, optionally narrowed to one number and a date range. Each record carries direction, duration, ring time, final outcome, recording URL where recorded, and any transcription, summary and sentiment score Voxloud produced. Paginated and sortable newest or oldest first.
Get Telephony Event Retrieve a single call detail record by event ID, including duration, outcome, recording URL, transcription and sentiment score where available.
Find Telephony Events By Call Retrieve every event belonging to one call ID. A single call produces multiple records as it is answered, transferred or forwarded, so this is the reliable way to reconstruct the whole conversation from a call ID captured by the trigger.

Click To Call

Create Click To Call Object Create a reusable click-to-call object binding an extension to an outbound caller ID. Voxloud caps how many can exist to the number of users plus groups on the account and recommends reusing them, so create these once and store the returned ID.
List Click To Call Objects Retrieve every click-to-call object with its bound extension and outbound caller ID. Used to find an existing object to reuse instead of consuming another slot.
Get Click To Call Object Retrieve one click-to-call object by ID, confirming which extension and caller ID it is bound to before a call is placed through it.
Delete Click To Call Object Permanently remove a click-to-call object and free one slot against the account quota. Any flow still referencing the deleted ID will fail, so references are retired first.
Start Click To Call Place a real outbound call through an existing click-to-call object, bridging the bound extension and the contact number supplied. This dials actual phone lines and incurs charges, so it sits behind explicit conditions. It returns as soon as Voxloud accepts the request, and the outcome arrives through the call events.

List WhatsApp Bots Retrieve the WhatsApp bots connected to the account with every registered message template, including each template's approval status, language, category and component structure. Used to discover which templates are approved before a flow references one.

Triggers

1 triggers

Event Triggers

On Call Event Fires when the selected Voxloud call event occurs on the PBX. This is a single trigger with a chosen event, not a separate trigger per event. Live events (Call Started, Call Incoming, Call Answered, Call Hangup) deliver the originator and destination numbers and names, the call ID and the handling extension. The completed-call events (Phone Call Completed, Fax Call Completed, Click To Call Completed) additionally deliver duration, ring time, direction, recording URL, transcription, summary and sentiment score. FlowRunner registers and removes the webhook subscription for you, and re-enables it if Voxloud disables it after failed deliveries.

Frequently Asked Questions

What can FlowRunner do with Voxloud?

FlowRunner agents can run Validate Credentials, List Users, and Create Contact in Voxloud, plus 13 more actions.

Does connecting Voxloud to FlowRunner require OAuth?

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

Can Voxloud trigger a FlowRunner workflow automatically?

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

Start building with Voxloud

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

Start Building Free Talk to us