Voiso
Voice & TelephonyRun agents, queues, campaigns, and omnichannel messaging on the Voiso cloud contact center. Agents staff against live demand and keep conversations attached to the right record.
What This Integration Enables
Voiso is a contact center for teams who run it as a line of business rather than a phone system. It is the only detail you need to understand the connector: every call record carries a cost, a wrap-up code, a queue, a campaign and per-stage durations covering dialing, IVR, queue, talk and hold time. That is not telephony data, that is unit economics. Alongside it sits omnichannel messaging, so a WhatsApp, Telegram, Instagram or web chat thread belongs to the same customer as the call.
FlowRunner agents work both sides. On the read side they stream call records into a warehouse with full attribution, pull speech analytics as structured segments or as a readable transcript, and reconcile scheduled callbacks against the CRM. On the write side they start calls, hang them up, send messages, load campaign leads and control campaigns, and every one of those writes spends money on a live phone network. The read side runs unattended. The write side is where automation exceptions surface, and where an agent should hand the decision to the person who owns the number.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Every call record becomes an attributed row
On New Call Record fires for each new call detail record, optionally narrowed to one direction and outcome. The agent takes the record, resolves the agent, queue and campaign, and writes a page into Notion or a row into the warehouse carrying cost, disposition, tags and the per-stage durations. Because the trigger can be filtered to abandoned or missed calls only, the same connector supports both a full backfill and a narrow watchdog without a second integration. For historical loads, List Call Records uses cursor pagination, which matters: offset paging is capped at the first ten thousand records, and a backfill built on offsets silently stops.
A support ticket that already contains the call
A customer calls in about an open ticket. When the call record appears, the agent calls Get Speech Analytics for the transcript, passes it to Anthropic for a short summary of what was agreed, and appends both the summary and the readable transcript to the ticket. The next agent to touch that ticket reads what happened rather than listening to a recording. Where a conversation started on WhatsApp and moved to a call, List Conversations and List Conversation Messages pull the earlier thread into the same ticket so the history is continuous.
A callback that is actually kept
A deal moves stage in HubSpot and the customer has asked to be called back on Thursday afternoon. The agent calls Create Scheduled Callback for the owning agent at the requested slot, and Voiso dials at that moment. A separate flow reads List Scheduled Callbacks each morning, compares upcoming commitments against agent availability, and flags any callback whose owner is on leave so a supervisor can reassign it before the customer notices.
Human-in-Loop Highlight
Control Campaign is where this connector stops being read-only. Starting a campaign does not queue a task, it begins placing real billable calls to every lead on the calling list at the configured dial level, and the calls are dialed and charged before anyone has a chance to reconsider. So the agent assembles everything and then asks. It loads the segment with Add Campaign Leads, reads the campaign's dialing configuration with Get Campaign, counts who is actually staffed with List Queue Members, checks Get Balance, and sends the contact center manager a single message: "Campaign 'Renewals West' is loaded with 4,310 leads at dial level 2.5, answering-machine detection on. Queue 'Renewals' has 6 of 11 agents signed in. Balance covers roughly the configured window. Start dialing, or hold?" The manager holds it until the afternoon shift signs in, and the agent starts it then. The agent did the assembly, the counting and the checking. The person who answers for the phone bill and for the abandoned-call rate made the one decision that carried both.
Agent Capabilities
22 actionsUsers
4- List Users Retrieve the agents and supervisors on the contact center with their SIP account, extension, caller ID, timezone, skills, assigned teams and queues, and the channels they are licensed to handle. Supports filtering on name, email, extension and access group.
- Get User Retrieve one agent or supervisor with their full profile, including channel capacity, skills, supervised teams and queues, and speech language. Used to check configuration before routing work to them.
- List Teams Retrieve the agent teams with their maximum call attempts and wrap-up code group. Teams are the usual unit for reporting and for scoping supervisor access.
- List Team Members Retrieve the agents belonging to one team. Used to fan work across a team, or to check staffing before a campaign that targets it.
Numbers
1- List Numbers Retrieve the provisioned numbers with label, type, country, city, channel count, provider, pricing, caller ID group membership and the inbound flow each is attached to. Used to audit number inventory and inbound routing.
Queues
2- List Queues Retrieve the routing queues with extension, distribution strategy, music on hold, in-queue announcement, failover destination, callback and post-call rating settings, and the channels and skills each serves.
- List Queue Members Retrieve the agents assigned to one queue. Used to confirm staffing before escalating volume to it, or to build an on-call list.
Reporting
4- List Call Records Retrieve call detail records with filtering on direction, outcome, wrap-up code, agent, team, queue, campaign, numbers, country and duration. Each record carries parties, cost, tags, timestamps and per-stage durations. Use cursor pagination for backfills, because offset paging is capped at the first ten thousand records.
- Get Call Record Retrieve one call detail record with its parties, outcome, cost, tags and per-stage durations across dialing, IVR, queue, talk and hold. Used to enrich an event once an ID is known.
- Get Speech Analytics Retrieve the speech analytics for calls, as structured JSON or as WebVTT, SubRip or plain-text transcripts. Used to attach a readable transcript to a ticket, or to feed structured segments to a summarization step.
- Get Balance Retrieve the current account balance. Used to alert on low credit before outbound campaigns stall mid-run.
Voice
2- Start Call Place a real outbound call by bridging an agent to a destination number. This dials live phone lines and incurs charges, so it belongs behind an explicit condition. Returns the call ID for later control or lookup.
- Hang Up Call Terminate an in-progress call by ID. Used to enforce a maximum call duration, or to end a call when a downstream system signals it is no longer needed.
Messaging
3- Send SMS Send a real, billable text message from the contact center to a destination number. Guarded behind explicit conditions in a flow.
- List Conversations Retrieve omnichannel conversations across WhatsApp, Telegram, Viber, Facebook, Instagram, SMS and web chat. Used to find an active thread before appending to it, or to report messaging volume by channel.
- List Conversation Messages Retrieve the messages inside one conversation, including text, media, contact and location content. Used to pull a full thread transcript into a ticket or a summary.
Campaigns
4- List Campaigns Retrieve outbound campaigns with dialing strategy, dial level, answering-machine detection, calling list, caller ID sets and follow-up rules. Filterable by name, live state or lead source system.
- Get Campaign Retrieve one campaign with its full dialing configuration, including dial level, maximum dial and wait times, answering-machine detection, follow-up rules and contact local-time handling.
- Control Campaign Start, pause or stop an outbound campaign. Starting begins placing real billable calls to its leads, so this is the action that carries a human decision. Pausing halts new dialing while leaving the campaign configured.
- Add Campaign Leads Add leads to a campaign's calling list. Each lead must match the campaign's configured lead schema, which always includes a phone number, and leads become dialable as soon as the campaign is live.
Callbacks
2- Create Scheduled Callback Schedule a callback for an agent to place at a future time. Voiso dials at the scheduled moment, so this eventually results in a real billable call. Used to honor a call-back slot a customer asked for somewhere else in a flow.
- List Scheduled Callbacks Retrieve scheduled callbacks with destination, owning agent, scheduled time, note and status. Used to report on upcoming commitments or reconcile them against the CRM.
Triggers
1 triggersEvent Triggers
1- On New Call Record Fires for each new call detail record that appears in Voiso, optionally narrowed to one direction and one outcome. Each event carries the full record, including both parties, the handling agent, queue and campaign, cost, tags and per-stage durations. Voiso offers no webhook management API, so this trigger polls the call records endpoint on a configurable interval. Filtering it to missed or abandoned calls turns the same trigger into a service-level watchdog.
Frequently Asked Questions
What can FlowRunner do with Voiso?
FlowRunner agents can run List Users, Get User, and List Teams in Voiso, plus 19 more actions.
Does connecting Voiso to FlowRunner require OAuth?
No. Voiso connects to FlowRunner with an API key, no OAuth flow required.
Can Voiso trigger a FlowRunner workflow automatically?
Yes. Voiso supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Voiso
$100 in credits. No card required. Connect in minutes.