peoplefone

Manage the peoplefone Swiss business VoIP PBX and send SMS. Agents provision extensions and numbers and keep call activity attached to the right record.

46 actions API key available

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

Scheduled check finds a cantonal holiday falling inside the next 48 hours

Agent resolves the holiday IVR and the current destination of each public number with Get Number

Agent confirms the holiday greeting on that IVR names the right date and reopening time

Agent verifies the emergency-address contact required for each number is still valid with List Number Contacts

Agent posts every number, where it rings today, and where it would ring tomorrow

The office manager confirms the diversion, and the agent applies it with Update Number Assignments

What This Integration Enables

Look at what peoplefone actually exposes and a theme appears immediately. Users, queues, groups, IVR menus, destinations, number assignments, smart routings, manual routings, time routings. Forty-something operations, and the large majority of them exist to answer or change one question: where does this call land? That is the honest positioning of this Swiss business PBX, and it is a more valuable question than it sounds, because in most companies nobody can answer it. The main number rings a group, which overflows to a queue, which overflows to an IVR, which has a key selection pointing at a user who left in March.

FlowRunner agents are good at exactly this. List Destinations returns every element a call can be routed to across the whole PBX, users, groups, queues, IVR menus, voicemail boxes, and all three routing types, each with its identifier and internal number, which means a flow can resolve the entire routing graph in one read and answer the question in plain language. From there the same agent can act on it: flip a manual routing to an out-of-office destination and back, repoint a public number at a holiday IVR, log a shift into its queues in the morning and out in the evening, and provision or remove a user as HR events arrive.

Two constraints shape how a flow should treat this connector. The Configuration API is vendor-flagged beta, so breaking changes are possible and a flow benefits from reading before it writes. And peoplefone validates queues, groups, and manual routings as a whole rather than field by field, so an update sends the complete configuration. That is a good argument for capturing current state as a first step, which conveniently is also what makes any change reversible.

Without FlowRunner

Nobody can say where a number rings Answering it means clicking through the portal and guessing at the routing chain

Holiday diversions set by memory Someone remembers to divert the main line, or remembers the morning after

Queues opened by whoever arrives The support line is live only once an agent thinks to log into it

With FlowRunner

The routing chain is readable One call to List Destinations resolves every element a call can land on

Diversions prepared in advance The change is assembled, checked, and waiting on a confirmation rather than on a reminder

Shifts open and close on schedule Agents are logged into their queues at the start of a shift and out at the end

Use Case Scenarios

Answering "Where Does This Number Ring?" in Seconds

Somebody in sales says a customer reached the wrong department. Instead of a portal expedition, an agent takes the dialled number, calls Get Number to find the element that answers it, then walks the chain with List Destinations, Get Group, Get Queue, and Get IVR with selections included. It returns a readable path: the number rings the Sales group, which rings three members one by one, overflows after 25 seconds to the Support queue, which overflows after four minutes to the main IVR, whose key 3 points at a user with no active line. The routing bug and the fix are visible in the same message, and the person who asked did not need PBX training to read it.

Shifts That Open and Close the Line

Support hours start at 08:00 and end at 17:30. An agent calls Log In Agent for each person rostered to that shift, scoped to the selected queues rather than everything they belong to, and Log Out Agent at the end. Get Agent Configuration and Update Agent Configuration set the grace periods after a missed and a completed call and the automatic Do Not Disturb rule, so an agent who misses several calls in a row is stepped out of the queue rather than left ringing into nothing. Through the day, Get Queue Statistics reports incoming, answered, abandoned, and overflowed counts with average and maximum wait, and the agent raises it with the supervisor when abandons move rather than at the end of the week.

Appointment Reminders with the Delivery Receipt Reconciled

A clinic sends appointment reminders the day before. The agent sends them with Send SMS, which accepts several recipients in E.164 format and returns a message identifier for each, and schedules them for a delivery time rather than firing at whatever hour the flow happens to run. It then polls Get SMS Message Status, which is lighter than the full record and suited to a loop, and reconciles each identifier against its appointment. Where a patient cancels after the message is queued but before it is sent, Cancel Scheduled SMS pulls it so it is never sent or billed, and peoplefone reports a conflict clearly if the send window has already passed.

Human-in-Loop Highlight

Update Number Assignments is the action on this connector that customers feel. It reassigns one or more public numbers inside a block, setting the emergency-address contact and the element that answers inbound calls, and the change takes effect on the next call that arrives. Point the main business number at the holiday IVR one day early and every customer who dials on a working Tuesday hears that the office is closed. Point it at a queue with no logged-in agents and the calls simply wait. There is no preview, no soft launch, and no way to know it went wrong except by someone calling the office to say so.

So a FlowRunner routing agent prepares the whole change and then pulls the digital andon cord. It resolves the target with List Destinations rather than trusting a stored identifier, reads the current destination of each affected number with Get Number so the message can state exactly what is changing, checks that the holiday greeting on the IVR names the correct date, and confirms the emergency-address contact each number requires is still valid with List Number Contacts, because a Swiss number carries a registered address for emergency calls and reassignment is where that gets lost. Then it stops: "3 public numbers would move from the Sales group to Holiday IVR from 18:00 Thursday until 07:00 Monday. Greeting says 'closed for Bundesfeier, reopening Monday'. Emergency contacts unchanged. Confirm?"

The office manager says yes, and the agent applies it. Every reversible step ran without asking, and the one step that changes what the outside world hears when it calls your company was decided by a person. That is what human-in-the-loop is for.

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

46 actions

Users

List Users Retrieves a paginated list of the users on the PBX with their identifier, display name, internal number, and entity type. Used to audit extensions or resolve a name to the identifier other operations expect.
Create User Provisions a new user and returns its identifier, choosing between a peoplefone HOSTED user with a hosted line and internal number, or a STANDARD line. The user is created with defaults, so a provisioning flow follows this with Update User.
Get User Retrieves the full configuration of one user: profile type, hosted line settings, alerting tones, contact language, description and email, the SIP user names on its lines, the caller ID shown on outgoing calls, and its incoming display settings.
Update User Updates an existing user, sending only the fields supplied. Renames a user, moves its internal number, changes its notification language and email, swaps the internal and external ringtones, or reconfigures caller ID display.
Delete User Permanently removes a user from the PBX. The extension stops receiving calls and any routing pointing at it breaks, so a flow verifies group memberships, queue agent rosters, and number assignments first. This cannot be undone.

Queues

List Queues Retrieves a paginated list of the call queues with their identifier, name, internal number, and entity type. Used to discover the identifiers the statistics and agent operations need.
Create Queue Creates a queue with its name, internal number, and distribution strategy. The time window applies only to the Shortest Time, Longest Idle, and Least Calls algorithms, where it must be 1, 4, or 8 hours; Round Robin and Ring By Priority ignore it.
Get Queue Retrieves one queue with its distribution strategy, ring settings, waiting music, waiting-time and capacity overflow rules, billing user, and caller ID display mode. Including agents also returns the roster with priority and membership.
Update Queue Updates a queue's configuration, covering distribution strategy, ring behaviour, minimum waiting-music play time, what happens at maximum wait or maximum waiting calls, the billed user, caller ID display, and the agent roster. peoplefone validates the queue as a whole, so send the complete configuration rather than a single field.
Delete Queue Permanently removes a queue. Calls routed to its internal number stop being answered and any routing pointing at it breaks, so numbers, IVR selections, and time routings should be checked first. This cannot be undone.

Queue Agents

Get Agent Configuration Retrieves the queue behaviour configured for one agent: the grace periods after a missed call and a completed call, and the automatic Do Not Disturb rule. A configuration is created automatically with every user, and including queues also lists the queues the agent belongs to.
Update Agent Configuration Updates how an agent is treated by their queues: the pause after a missed call, the pause after a completed call, and how many consecutive missed calls within a window push the agent into Do Not Disturb. All four values are required, so send the complete configuration.
Log In Agent Logs an agent into their queues so they start receiving queued calls, either all queues they belong to or a selected list. This is how a support line opens at the start of a shift without anyone remembering.
Log Out Agent Logs an agent out of their queues so they stop receiving queued calls, either everywhere or from a selected list. Pairs with Log In Agent to close the line at the end of a shift.

Groups

List Groups Retrieves a paginated list of the call groups with their identifier, name, internal number, and entity type. Groups ring several destinations together and are the usual target for a main business number.
Create Group Creates a call group with its name, internal number, and ring strategy. Ring All alerts every member at once; One By One walks the members in order.
Get Group Retrieves one group with its ring strategy, alerting tone, overflow rules, and advanced settings. Including members also returns each step with its destination, position, per-destination timer, and whether it follows call forwarding.
Update Group Updates a group's name, internal number, ring strategy, alerting tone, and advanced settings, and configures what happens when nobody answers within the overflow timer. peoplefone validates the group as a whole, so the name, internal number, ring strategy, and alerting tone travel with any change.
Delete Group Permanently removes a call group. Members are not deleted, but calls to the group's internal number stop being answered and any number or routing pointing at it breaks. This cannot be undone.

IVR Menus

List IVRs Retrieves a paginated list of the IVR menus with their identifier, name, internal number, and entity type. Used to discover the identifiers referenced by numbers, groups, and queue overflow rules.
Create IVR Creates an IVR menu with a name, internal number, and billed user. The menu is created empty, so a flow follows with Update IVR for the greeting and uses the portal to attach key selections.
Get IVR Retrieves one menu with its greeting configuration, ringtone setting, and billing user. Including selections also returns the key mapping, which is the step that shows where each digit a caller presses actually sends them.
Update IVR Updates a menu's name, internal number, ringtone setting, billing user, and text-to-speech greeting. When text to speech is enabled peoplefone requires both a voice identifier and the message text together.
Delete IVR Permanently removes a menu together with its key selections. Any number, group, or queue overflow pointing at it stops routing. This cannot be undone.

Numbers and Destinations

List Destinations Retrieves every element a call can be routed to across the PBX, spanning users, groups, queues, IVR menus, voicemail boxes, and the three routing types, each with its identifier, name, internal number, and entity type. This is the fastest way to resolve a name to the identifier a routing operation expects, and the foundation of any answer to where a number rings.
Get Number Block Retrieves a block of public numbers with its porting-in and porting-out dates. Including numbers also returns every number in the block with its emergency-address contact and the element inbound calls currently reach.
Update Number Assignments Reassigns one or more public numbers inside a block, setting the emergency-address contact and the element that answers inbound calls. Only the numbers supplied are changed, and the change takes effect on the next inbound call. This is the action that reaches the outside world, so it belongs behind a named human confirmation.
Get Number Retrieves the configuration of a single public number by its DID, returning its block, emergency-address contact, and the element that answers inbound calls. Used to state exactly what is changing before anything changes.
List Number Contacts Retrieves the contacts that can be attached to a public number, each with its identifier and formatted address. These carry the registered address used for emergency calls, so one is chosen before a number is reassigned.

Routing

List Smart Routings Retrieves a paginated list of the smart routings on the PBX. A smart routing hands the routing decision to an external service, so this shows which ones exist before their configuration is inspected.
Get Smart Routing Retrieves one smart routing with the URL of the external service that makes its decisions and the fallback applied when that service does not answer in time, including the maximum wait and the forwarding destination.
List Manual Routings Retrieves a paginated list of the manual routings. A manual routing is a switch an administrator flips between prepared rules, typically to move calls to an out-of-office destination.
Create Manual Routing Creates a manual routing with its name, internal number, mode, on or off state, and rule set. Standard mode offers a single alternative destination while Advanced mode allows several named rules.
Get Manual Routing Retrieves one manual routing with its mode, current state, and billing user. Including rules also returns the named rules and the destination each one diverts to. The state is reported in lowercase even though it is written in capitalised form.
Update Manual Routing Updates a manual routing, most often to flip its status so a flow can divert calls to an out-of-office destination and back. peoplefone validates the routing as a whole, so the name, internal number, mode, and status travel together, and supplying rules replaces the existing rule set.
Delete Manual Routing Permanently removes a manual routing together with its rules. Any number or menu selection pointing at it stops routing. This cannot be undone.
List Time Routings Retrieves a paginated list of the time routings. A time routing sends calls to different destinations depending on opening hours and holiday exceptions.
Create Time Routing Creates a time routing with a name, internal number, and description. The routing is created without schedules or exceptions, which are configured afterwards in the portal.
Get Time Routing Retrieves one time routing with the destination used outside opening hours, its weekly schedules, its date exceptions such as public holidays, and its advanced settings including the billed user and caller ID display mode.

SMS

List SMS Messages Retrieves the account's SMS history in both directions, with each message's identifier, status, sender, recipient, and the times it was received, scheduled, sent, and delivered. Filter by status to find everything still scheduled or everything that failed. Paging here is zero-based.
Send SMS Sends a real, billable message through the peoplefone SMS gateway to one or more recipients in E.164 format, returning an identifier for each. Encoding is chosen automatically, giving up to 1530 characters for plain GSM text and 670 when special characters force Unicode. Supplying a future delivery time schedules the message rather than sending it immediately.
Get SMS Message Retrieves the full record of one message, including status, sender, recipient, and the times it was received, scheduled, submitted, and delivered. Used to reconcile a send against the delivery receipt.
Get SMS Message Status Retrieves just the current delivery state of one message with its direction and the time the state last changed. Lighter than the full record, so it suits polling a scheduled or in-flight message inside a loop.
Cancel Scheduled SMS Cancels a message still scheduled for future delivery so it is never sent or billed. peoplefone rejects the call with a conflict once the message has left the scheduled state, and this operation reports that clearly, so a flow checks status first when the send window is close.

Statistics

Get Queue Statistics Retrieves summary statistics for one queue over a period, bucketed by the chosen aggregation: incoming, answered, abandoned, and overflowed counts, average and maximum waiting, abandon, and talk times, and ringing attempts. Only completed calls are counted, and the period may not exceed six months.
Get Agent Statistics Retrieves statistics for one agent over a period, optionally limited to specific queues: incoming and answered calls, ringing attempts, average and maximum response time from first ring to answer, and total, average, and maximum talk time. The period may not exceed six months.

Frequently Asked Questions

What can FlowRunner do with peoplefone?

FlowRunner agents can run List Users, Create User, and Get User in peoplefone, plus 43 more actions.

Does connecting peoplefone to FlowRunner require OAuth?

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

Can peoplefone trigger a FlowRunner workflow automatically?

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

Start building with peoplefone

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

Start Building Free Talk to us