IPEX

Work with the IPEX Czech VoIP and PBX platform, covering call records, live call control, recordings, transcripts, and contact centre reporting. Agents attach call evidence to the record it belongs to.

33 actions API key available

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

Nightly retention job runs against the previous day's call audio

Agent lists the recordings stored in the window and resolves each filename back to its call

Agent flags any recording attached to an open dispute, complaint, or legal hold

Agent separates the files that are genuinely past the retention window from the ones that are not

Agent posts the proposed purge list and the held-back exceptions to the compliance channel

The records owner confirms the list, and the agent runs Delete Recordings against exactly what was approved

What This Integration Enables

IPEX is a Czech VoIP and PBX platform, and the reason it earns a connector rather than a webhook is that it treats a phone call as a record with a life cycle, not as an event that happens and disappears. Every call carries a detail timeline, a recording, a speech-to-text transcript split by stereo channel, a queue it passed through, and an agent who handled it. FlowRunner agents read all of that, which means the call stops being something a person remembers and becomes something a flow can act on: attach the transcript to the deal, score the queue against the service level, push the survey result back onto the call record with Update Call.

The second half of the surface is live. List Current Calls returns the conversations happening right now with the channel identifiers that Hang Up Call, Transfer Call, and Monitor Call act on. That is a real capability and also a real hazard, because those operations touch a conversation a customer is in the middle of. This is exactly the boundary FlowRunner is built for. The agent can read the whole call estate continuously and act on it without hesitation where the action is reversible, and it stops and asks a person where the action is not. Reading a transcript is free. Cutting a live call, or deleting the audio that proves what was said, is not.

Without FlowRunner

Audio accumulates unattended Recordings pile up on the PBX with no running view of what is past retention

Purge happens by hand Someone works through filenames in the admin console when an audit reminder lands

Evidence sits apart from the record The call that settled a dispute stays in the phone system instead of on the case

With FlowRunner

Inventory on a schedule The agent reads the recording window nightly and knows what is eligible before anyone asks

Deletion behind a named approval Nothing is removed until a person with the authority to remove it confirms the list

Transcript on the case Calls arrive on the record they belong to with the text already separated by speaker

Use Case Scenarios

Missed Support Calls Become Written Follow-Ups

Every morning an agent pulls the previous day's abandoned queue calls with List Missed Calls, which returns the caller ID, the queue, the hold time, and anything the caller keyed into the IVR before giving up. For the calls that connected long enough to leave audio, the agent pulls Get Call Transcript, reads the customer channel separately from the agent channel, and drafts a follow-up per caller with the reason they called already summarized. The support lead opens a single queue of drafts rather than a list of phone numbers with no context. The work shifts from reconstructing what happened to deciding what to say.

Queue Service Level Watched Continuously

Get Queues Report returns per-queue totals with a configurable service level threshold, average and maximum wait, and how many calls were answered outside the target. An agent polls it through the day, and when a queue crosses the threshold it does not just alert. It calls List Transfer Destinations, which reports the number of free agents and each agent's call centre state, and List Members to see who else is trained on that queue. The message to the supervisor names the queue, the current wait, and the two agents on another queue who could cover it. The supervisor makes the staffing call with the answer already assembled.

Post-Call Outcome Written Back to the Call

A CRM records the outcome of a sales call: won, lost, or a callback booked. An agent takes that outcome, resolves the matching IPEX call with List Calls filtered on the customer number, and writes the result back with Update Call as a one to five rating, a success flag, and a note. Six months later the contact centre report and the CRM tell the same story, because the outcome lives on both sides. Anyone auditing a deal can move from the pipeline record to the call detail timeline in Get Call Detail without a spreadsheet in between.

Human-in-Loop Highlight

Delete Recordings is the operation on this connector that a flow should never run unsupervised. It removes audio in bulk, up to 1000 filenames or call identifiers per request, and it will also take a filter over user extensions and a time window, which means one badly scoped call can erase a month of a team's audio. IPEX is explicit that deletion cannot be undone. So a FlowRunner retention agent builds the whole case and then stops: it posts the count of files it intends to remove, the date range, the extensions covered, and the specific calls it held back because they are attached to an open complaint, then asks the records owner in Slack, "Purge these 412 recordings from 1 to 31 May? 9 files are excluded because their calls are on an open dispute. Confirm, or tell me which to keep." The agent has done every part of the job that is reversible. The one step that is not stays with the person who is accountable for it. That is human-in-the-loop applied where it actually matters, rather than an approval box in front of a harmless read.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

33 actions

Call History

List Calls Retrieves call detail records with source, destination, line, trunk, duration, billed seconds, disposition, direction, and recording filename. Every text filter is paired with a match mode, so a number can be matched exactly or by prefix, suffix, or substring. Used as the entry point for any flow that needs to find a specific customer's calls.
Get Call Detail Retrieves the ordered event timeline for one call, showing each stage such as ringing, answer, queue entry, and hangup with the source and destination active at that moment. Used to reconstruct exactly how a call travelled through the PBX when someone disputes what happened.
List Current Calls Retrieves the calls live on the PBX right now with their channel ID, both numbers, direction, ringing or connected state, and elapsed duration. The channel ID it returns is what the hangup and monitor operations act on, so this is the first step in any live call automation.
List Missed Calls Retrieves missed and abandoned calls from the call centre queues, matching what agents and supervisors see in their panel. Each record carries the caller ID, queue, hold time, inbound and callback attempt counts, any value captured in the IVR, and whether the call is still awaiting handling. Used to drive callback and follow-up flows.
Update Call Writes agent-supplied metadata back onto a finished call: a one to five customer rating, a customer success flag, and a free-text note. Used to push a survey result or a CRM outcome back into the IPEX record so both systems agree.

Live Call Control

Create Call Places a real, billable outbound call on the PBX. The originating side rings first and the destination is dialled once it answers. Every run dials a live number, so this belongs behind explicit conditions in a flow. Returns the call ID and the channel ID needed to hang the call up again.
Hang Up Call Immediately terminates a call in progress, cutting off a live conversation. The call is identified by channel ID, call ID, or user ID. Used in supervisor tooling and in fraud response, always with List Current Calls first to resolve the identifier.
Transfer Call Moves a live caller to another destination. A blind transfer hands the caller over immediately; an attended transfer first connects the transferring agent to the destination so they can announce the call. Used when a flow can determine the right destination faster than the agent handling the call can.
Cancel Attended Transfer Aborts an attended transfer still in progress, returning the caller to the agent who started it. Only meaningful while the announcement leg is still up.
Monitor Call Joins a live conversation for supervision, either listening silently or whispering to the agent so only they can hear. This connects a real audio leg to an ongoing call, so recording and privacy rules govern whether it can be automated at all.
List Transfer Destinations Retrieves the destinations a call may be transferred to, covering users and applications such as queues and IVRs. Each entry carries the extension plus, for queues, the number of free agents and the agent's call centre state, so a flow can pick the destination most likely to answer rather than the one that happens to be first.

Recordings and Transcripts

List Recordings Retrieves the names of recordings stored on the PBX within a time window, paged at up to 1000 filenames. Feeds retention flows, archive exports, and quality sampling.
Get Call Recordings Retrieves the recordings attached to one call, each with its filename and the two numbers on that leg. Used when a flow already knows the call and needs the audio for it.
Get Call Transcript Retrieves the speech-to-text transcript of every recording belonging to one call, segmented by stereo channel with start and end offsets. Channel separation is what makes the transcript usable, because the agent's words and the customer's words arrive already told apart before any summarization or sentiment step runs.
Get Recording Retrieves a playable link for a single recording by filename. Used when a person needs to listen rather than a flow needing to process.
Download Call Recordings Retrieves every recording belonging to the supplied calls bundled into a single zip archive, up to 50 call identifiers at once. Used for archiving a day of calls or handing a batch to a reviewer.
Delete Recordings Permanently deletes recordings in bulk, selected by filename, by call identifier, or by a filter over extensions and a time window. Deletion cannot be undone, and the response separates the files removed from those that failed. This is the operation that should sit behind a named human approval in every flow that uses it.

Availability Profiles

List Profiles Retrieves the availability profiles defined for users, showing whether each is active, how it handles calls, any forwarding target, and the device it rings. Profiles are how IPEX models states such as at desk, on mobile, or unavailable.
Update Profile Changes a profile's settings: active state, forwarding target, and the device endpoint it rings. Used to build shift and out-of-office behaviour that follows a schedule instead of a person remembering.
Delete Profile Permanently removes an availability profile. Any user assigned to it falls back to their remaining profiles, so a flow should confirm assignments before running this unattended.
Set User Profile Applies an availability profile to a user, which immediately changes how their incoming calls are routed. Used to open and close individual lines on a schedule.

Contact Centre Reporting

Get Calls Report Retrieves extended per-call reporting rows covering the IVR entered, the queue, the handling user, direction, answered state, waiting and ringing time, hold time, queue position, and any callback that followed. This is the richest call view IPEX exposes and the right source for service quality dashboards.
Get Queues Report Retrieves per-queue statistics for a period: total, answered, and unanswered calls, how many were answered inside and outside the service level target, and average and maximum wait and talk times. The service level threshold is configurable in seconds.
Get Agent Activity Report Retrieves the raw agent activity log, one row per event such as logging into a queue, pausing, unpausing, or completing a call. Used for adherence auditing, filtered by queue, agent, or event type.
Get Agent Activity Durations Report Retrieves how each agent spent the reporting period, split into seconds on incoming calls, outgoing calls, paused time, logged-in time, and idle time, alongside the queues they were logged into. Used to compare occupancy across a team without exporting anything by hand.
Get Agent Daily Stats Retrieves today's per-agent statistics since each agent logged in: calls taken, answered and unanswered outgoing calls, callbacks made, total talk time, failed rings, and billed and unbilled pause time. Suits a live wallboard or a shift-end summary.

Administration

Reload Service Applies pending configuration changes to the PBX. A full reload restarts the whole configuration and can briefly disturb service, while a modular reload refreshes only what changed. Run after configuration edits so they take effect, and prefer the modular form inside business hours.

Frequently Asked Questions

What can FlowRunner do with IPEX?

FlowRunner agents can run List Calls, Get Call Detail, and List Current Calls in IPEX, plus 30 more actions.

Does connecting IPEX to FlowRunner require OAuth?

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

Can IPEX trigger a FlowRunner workflow automatically?

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

Start building with IPEX

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

Start Building Free Talk to us