Cloudonix
Voice & TelephonyManage calls, voice applications, numbers, subscribers, and trunks on Cloudonix. Agents provision telephony infrastructure and route calls as part of a larger operational workflow.
What This Integration Enables
Cloudonix is not an application with a phone feature bolted on. It is the call path: domains, SIP trunks, subscriber endpoints, inbound DNIDs and the voice applications those numbers hand calls to. Most teams that run on it have exactly one or two people who genuinely understand the routing, and everything that touches it happens in a cockpit at the moment something is already going wrong.
This connector puts that plane behind FlowRunner connectors so an agent can do the reading, the correlation and the proposal, while the change itself waits for a person. An agent can place a real call with Place Call and hand it to a named voice application, a CXML URL or a literal CXML document. It can read sessions with the full profile Cloudonix assembled, including the terminating trunk, the SIP headers on each leg and the last error, which is what turns "calls are failing" into "calls on this trunk are failing with this cause". It can pull mixed or raw recordings for transcription, provision and suspend subscribers, audit which cockpit users and API keys can change routing, and compare the concurrency limit against live sessions before a flow starts a batch of outbound calls. What it does not do is quietly repoint production traffic, because Update Number, Update Voice Application and Update Trunk all change live call behaviour the instant they succeed.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Diagnosing and rerouting a degraded trunk
Outbound calls to one country start failing. On its scheduled sweep the agent runs List Call Sessions filtered to failed status, reads the last error and the terminating trunk from each session profile, and finds the failures clustered on a single trunk rather than spread across the estate. It runs Get Trunk to confirm the host and active state, and Get Concurrency Limit compared against the count of connected sessions to rule out simply hitting the ceiling. It then runs List Trunks to identify a viable alternative and posts the whole picture to the voice channel: the failing trunk, the error, the sample sessions, and the proposed change. The engineer approves, and only then does Update Trunk run.
Call audio into transcription with speaker attribution
A compliance review needs the audio from a specific set of sessions. The agent runs Get Call Session to confirm each one completed and carries recordings, then chooses its source deliberately. Where a plain transcript is enough it runs List Session Recordings for the mixed audio. Where the review needs to know who said what, it runs List Session Raw Recordings instead, because the raw recordings keep each leg separate and let the transcription step attribute speech to a party. The resulting URLs go straight to transcription and the output is filed against the customer record.
Endpoint provisioning that fails safe
A support team's softphone estate is driven from the identity system. When someone joins, the agent runs Get Subscriber to check the MSISDN is free, then Update Subscriber to create the endpoint. When someone leaves, it does not run Delete Subscriber. It runs Update Subscriber to mark the subscriber inactive, which stops the device signing in and stops calls routing to it while keeping the identity available if the person returns or the number needs to be reclaimed deliberately. On a schedule the agent also runs List Domain Users and List API Keys and posts anything unrecognised, because the list of who can change call routing is worth watching even when nothing is broken.
Human-in-Loop Highlight
Update Voice Application changes call control for every number pointed at that application, and it takes effect on the next call. There is no staging environment between the write and a real caller hearing the result. So when an agent concludes that an application should point somewhere else, escalating to a failover URL because the primary is timing out, it treats the write as the gate rather than the conclusion. First it runs List Application Numbers, which returns the DNIDs currently routing into that application, so the proposal carries its own blast radius. Then it asks the voice owner directly: "Application main-ivr is returning errors on 14 of the last 20 sessions. Nine numbers route into it, listed below, including the main sales line. Proposed change points it at the failover URL. Apply?" The engineer answers, the agent runs Update Voice Application, and re-reads the next sessions to confirm the calls are landing. This is the digital andon cord applied to the phone network: the agent is allowed to stop the line and show its work, and a person decides whether to pull the lever.
Agent Capabilities
27 actionsPlacing and Inspecting Calls
4- Place Call Places a real, billable outbound call from the configured domain and hands it to call control. Exactly one of Application, URL or CXML says what happens once the call connects. Caller ID, DTMF digits to send on answer, a progress callback URL, a hard duration cap and explicit routes are all optional. Guarded behind an explicit condition in a flow.
- List Call Sessions Retrieves sessions with destination, caller ID, direction, status, the profile Cloudonix built, timings for start, answer and end, and the last error. Used as the polling surface for failure detection and post-call workflows, since the domain publishes no webhook subscription API.
- Get Call Session Retrieves one session by token with the full assembled profile: terminating trunk, errors raised, SIP headers on the session and on the subscriber and trunk legs, and attached recordings. Used to answer why a specific call ended the way it did.
- Get Concurrency Limit Retrieves how many simultaneous calls the account may run. Compared against connected sessions before a flow starts a batch, so the batch does not hit the ceiling mid-run.
Recordings
2- List Session Recordings Retrieves media URLs for the mixed recordings of a session. The normal route to the audio of a completed call, handed straight to transcription or archiving.
- List Session Raw Recordings Retrieves media URLs for the raw, unmixed recordings where each leg is kept separately. Used when transcription needs to attribute speech to a specific party.
Voice Applications and Routing
5- List Voice Applications Retrieves the voice applications defined on the domain. These are the named call-control entry points that Place Call and inbound numbers hand calls to.
- Get Voice Application Retrieves one voice application by name, including the URL or logic it points at. Used to confirm what a call handed to that application will actually do before changing anything.
- Update Voice Application Creates or updates a voice application under a given name. Changes live call control for every number pointed at it, so it runs only after approval.
- Delete Voice Application Permanently removes a voice application. Numbers still pointing at it stop being handled correctly, so List Application Numbers is checked first.
- List Application Numbers Retrieves the DNIDs that route inbound calls into one voice application. Run before any application change to see exactly which numbers the change will affect.
Numbers
4- List Numbers Retrieves the DNIDs on the domain, meaning the inbound numbers or number patterns Cloudonix matches an incoming call against before handing it to a voice application.
- Get Number Retrieves one DNID, showing whether it is active, whether it is a literal number or a matching expression, and which voice application it routes to.
- Update Number Creates or updates a DNID, which is how a number is pointed at a voice application or taken out of service. Changes live inbound routing immediately.
- Delete Number Permanently removes a DNID, after which inbound calls to that number are no longer matched. Marking it inactive with Update Number is preferred when the number may be reused.
Subscribers
4- List Subscribers Retrieves the endpoint identities registered on the domain, typically SIP devices or softphone users, keyed by MSISDN.
- Get Subscriber Retrieves one subscriber by MSISDN with its active state and profile data. Used to confirm an endpoint exists before routing a call to it.
- Update Subscriber Creates or updates a subscriber at a given MSISDN. Used to provision an endpoint, or to suspend one by setting it inactive rather than deleting it.
- Delete Subscriber Permanently removes a subscriber. Devices registered as that subscriber stop signing in and calls can no longer route to it.
Trunks
4- List Trunks Retrieves the SIP trunks on the domain. Trunks are the carrier connections outbound calls terminate over, and a session profile names the trunk that carried it.
- Get Trunk Retrieves one trunk by UUID with its host and active state. Used to expand the terminating trunk recorded on a session profile.
- Update Trunk Creates or updates a SIP trunk. Affects how every outbound call on the domain terminates, so it is treated as a change-controlled operation rather than routine automation.
- Delete Trunk Permanently removes a trunk. Outbound calls that relied on it fail to terminate until routing changes, so an alternative is confirmed in place first.
Account and Access
4- List Domain Users Retrieves the cockpit users with access to the domain, distinct from subscribers. Used to audit who can change call routing.
- List API Keys Retrieves the API keys issued for the domain with identifiers and creation dates. Secrets are not returned, so this is an audit surface for spotting stale credentials.
- Get Account Retrieves the customer account the API key belongs to with its name and state. Used as a connection health check at the start of a flow.
- List Account Domains Retrieves every domain on the account, not only the configured one. Used to discover the correct domain for a connection or to audit the estate.
Frequently Asked Questions
What can FlowRunner do with Cloudonix?
FlowRunner agents can run Place Call, List Call Sessions, and Get Call Session in Cloudonix, plus 24 more actions.
Does connecting Cloudonix to FlowRunner require OAuth?
No. Cloudonix connects to FlowRunner with an API key, no OAuth flow required.
Can Cloudonix trigger a FlowRunner workflow automatically?
Cloudonix doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Cloudonix
$100 in credits. No card required. Connect in minutes.