FlowRunner
PricingContact
Theme
Start Free

Manage numbers, extensions, contacts, and call data on the Placetel cloud phone system by Cisco. Agents keep telephony configuration in step with the team and log calls against the right record.

21 actions API key available
Placetel website ↗ Platform Documentation ↗ Capability data verified 2026-08-02
A monthly telephony review starts on a schedule
Agent reads the full number inventory with List Numbers and the extensions behind it with List SIP Users
Agent cross-references List Calls and List Call Detail Records to find numbers with no inbound activity and a running cost
Agent confirms each candidate's current routing assignment with Get Number before proposing any change
Agent posts the shortlist with each number's last inbound call, its routing target and its charged spend
The telephony owner confirms which lines go dark, and only then does the agent run Deactivate Number

What This Integration Enables

Placetel is a German cloud phone system from Cisco, and the thing worth automating about it is not the calling. It is the estate. Numbers per site, SIP extensions per person, ring-all and hunt groups per team, call center queues, and a bill that grows quietly as campaigns come and go. FlowRunner agents read all of it: the number inventory with its routing assignment and activation state, the extensions with their live registrations, the call groups with their distribution strategy, and the call detail records that carry the charged amount and the tariff description for every leg.

The write surface is deliberately narrow, and that shape tells you what this connector is for. Agents can activate and deactivate a number, place a call from a named extension, send a text message, and register or remove webhook subscriptions. Everything else is reading, reconciling, and putting a decision in front of the person who owns the estate. That is the point. A phone system is one of the few pieces of infrastructure where a wrong configuration change is invisible to you and immediate to your customer, so the agent does the reconciliation and stops before the change.

Without FlowRunner

Unowned number estate Nobody can say which lines are live, where they route, or what each one costs
Spend reviewed once a year Billing-grade call detail records sit in a portal only the person who set it up opens
Config changed blind A line is switched off without anyone checking where it is still published

With FlowRunner

Inventory reconciled on a schedule Numbers, extensions and call groups are read back against actual call activity
Cost attached to each line Charged amounts and applied tariffs land next to the number they belong to
Deactivation behind a decision Nothing goes dark until the person who owns that line says so

Use Case Scenarios

Dormant number audit with real cost attached

Most telephony cleanups stall because nobody can connect a number to what it costs. An agent runs the two halves together: List Numbers returns the inventory with prefix, routing assignment, carrier and activation state, and List Call Detail Records returns billing-grade rows carrying the charged amount and a description of the tariff applied. The agent joins them, filters to numbers with no inbound traffic across the review window using List Calls, and produces a shortlist where every candidate carries its cost, its last real call, and where it currently routes. The operations lead reads a decision list instead of a spreadsheet export.

Call recordings into a searchable record

Placetel returns recordings as hosted file URLs rather than as binary, so an agent never has to download the audio to move it. List Recordings gives the two parties, the duration, the timestamp and the URL. The agent hands that URL straight to a transcription step in Speechmatics or Deepgram, summarizes the conversation, and writes the summary against the matching CRM record. Where the caller is not yet known, List Contacts resolves them from the phonebook by searching across every stored phone field.

Ring the owning rep the moment a deal is created

A deal is created in Pipedrive. The agent resolves the owning rep's extension with List SIP Users, checks List Call Center Agents to confirm the rep is actually reachable rather than offline, and runs Initiate Call, which rings the rep's extension first and then connects them to the prospect. If the rep is unavailable, the agent posts to Slack instead of dialing a desk nobody is sitting at, and the call stays queued as a task rather than becoming a missed connection nobody logs.

Human-in-Loop Highlight

The gate on this connector is Deactivate Number, and it earns the gate because it looks harmless. Deactivating a number leaves its routing configuration completely intact, so the change reads as reversible in the portal and reads as a dead line to anyone dialing it. The number may still be printed on an invoice, a service van, a Google listing, or a contract signed two years ago. So the agent assembles the case and stops: it posts the shortlist to the telephony owner with the exact question, "These four numbers took no inbound calls in the last 90 days and cost 41 euros last month. Number 0221 5000 4471 routes to the Cologne support group. Confirm which of these should stop accepting calls." The owner ticks the ones that are genuinely retired. The agent runs Deactivate Number only on that set, and leaves the rest alone. This is what human-in-the-loop looks like on infrastructure: the agent does the reconciliation nobody has time for, and a person owns the change that a customer would feel.

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

21 actions

Account and Users

2
  • Get Account Returns the account behind the configured API key, including the company, the platform and the primary SIP user. Used as a connection check and to confirm which tenant a flow is operating against before it changes anything.
  • List Users Returns the web users on the account, optionally narrowed to the main account holder or to sub users. Used to audit who still has portal access.

Numbers

4
  • List Numbers Returns the phone numbers on the account with their E.164 form, area prefix, routing assignment, carrier and activation state. Filterable by prefix, exact number, name, description, site or activation status, which makes it the starting point for any inventory audit.
  • Get Number Returns one number by its Placetel ID with its routing assignment, site and activation state. Used to confirm where a line currently routes before proposing a change to it.
  • Activate Number Brings a number back into service so it accepts calls again under its existing routing plan. Used to reopen a seasonal or overflow line without rebuilding its configuration.
  • Deactivate Number Takes a number out of service so it stops accepting calls, while leaving its routing configuration intact. Used to close a campaign line at the end of its window, and gated behind an approval because a deactivated number is silent to whoever dials it.

Extensions and Groups

2
  • List SIP Users Returns the SIP extensions with their SIP UID, assigned direct dial number, caller ID, routing plan, online state and current registrations. The SIP UID returned here is what Initiate Call needs in order to dial from a specific desk.
  • List Groups Returns the call groups with their distribution strategy: ring-all groups alert every member at once, hunt groups pass the call along in sequence, and monitoring groups exist for supervision. Used to work out where a number's calls actually land.

Call Activity

4
  • List Calls Returns inbound calls for a single day with both numbers, duration, resolved contact, unread state and a recording URL where one exists. Placetel defaults this filter to today, so historical reporting passes an explicit date.
  • Initiate Call Places a real outbound call by ringing the given SIP extension first and then connecting it to the target number. This dials live phone lines and incurs call charges, so flows guard it behind explicit conditions.
  • List Call Detail Records Returns billing-grade records for a day, each carrying the charged amount, the tariff applied, both parties and the billed length. Used for cost reporting and reconciliation, where List Calls covers activity.
  • List Recordings Returns recordings with both parties, duration, timestamp and a downloadable URL. Because Placetel serves a hosted link rather than binary, the file can be passed straight to a transcription or archiving step.

Call Center

3
  • List Call Center Agents Returns the call center agents with their availability, whether they are a supervisor or an agent, and whether they are reachable over SIP or the public telephone network. Used to check staffing before routing work into a queue.
  • List Call Center Queues Returns the queues configured on the account. Used to discover queue identifiers before reporting on them or filtering call center activity.
  • List Call Center Calls Returns queue activity showing which queue each call entered, which agent took it, when it left the queue and how it ended. Used to measure abandonment and to find calls that were never assigned to anyone.

Contacts and Faxes

2
  • List Contacts Returns phonebook contacts with names, company, every stored phone and email field, speed dial digit, tags and blocked state. Supports a number search across all phone fields and an updated-since window for incremental synchronization.
  • List Faxes Returns inbound and outbound faxes with sender, recipient, direction and delivery status. Used to confirm delivery or to pick up newly received faxes for downstream processing.

Messaging

1
  • Send SMS Sends a text message from the account to a single recipient. This is a real, billable message, so flows guard it behind explicit conditions.

Webhooks

3
  • List Webhook Subscriptions Returns the registered webhook subscriptions with their callback URL, subscribed events and any number restriction. Requires the Placetel Profi plan.
  • Create Webhook Subscription Registers a subscription so Placetel posts call events to your own endpoint, optionally restricted to specific numbers. Placetel does not publish the delivered payload schema, so inspect a live delivery before depending on specific fields. Requires the Placetel Profi plan.
  • Delete Webhook Subscription Removes a subscription so Placetel stops posting to its callback URL. Used to clean up retired endpoints. Requires the Placetel Profi plan.

Frequently Asked Questions

What can FlowRunner do with Placetel?

FlowRunner agents can run Get Account, List Users, and List Numbers in Placetel, plus 18 more actions.

Does connecting Placetel to FlowRunner require OAuth?

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

Can Placetel trigger a FlowRunner workflow automatically?

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

Start building with Placetel

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