PingBell
CommunicationRing a PingBell virtual doorbell to increment its live counter on every paired screen, from phones to Apple TV and Fire TV. Agents raise a visible, physical-feeling alert on the floor when something needs attention now.
What This Integration Enables
PingBell is not a messaging tool, and reading it as one will lead you to build the wrong thing. Ringing a PingBell increments its live counter on every paired screen, phones, desktops, Apple TV, Fire TV, Android TV and Roku, and pushes a notification with that PingBell's own sound to everyone subscribed to it. It is a floor alert with a physical feel: a number that visibly ticks up on the screen on the wall, and a sound people learn to recognize from across a room.
The consequence for flow design is unusual and worth stating plainly. The flow sends no text. Notification wording and sound are configured per PingBell inside the PingBell app, so ringing one takes only its identifier. Every bit of meaning a ring carries comes from which bell rang. That makes this connector two actions wide and deliberately so: List PingBells resolves a bell by name, so one flow can serve several teams, and Ring PingBell fires it. If the people who hear it also need the detail, the detail goes somewhere else in the same flow, into a chat channel or a dashboard, and the bell does the job the chat channel cannot do, which is to make the room look up.
FlowRunner's digital andon cord is the idea that an agent should stop the line when it hits something it should not decide alone. PingBell is one of the few places in the catalog where pulling that cord can be heard rather than read. It is also, for the same reason, one of the few where a human-in-the-loop step earns its keep by deciding what the agent is allowed to interrupt everyone for.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The sales floor hears the order, not the dashboard
An order lands in Shopify or a subscription starts in Stripe. The agent checks it against the rule the floor set, new business above a value the team agreed on, and rings the sales bell. Everyone in the room hears the same sound and watches the same counter move. In the same run the agent posts the account, the amount, and the rep into the sales channel, because the ring says that something happened and the channel says what. Two surfaces, one flow, no one refreshing a dashboard.
An escalation that cannot be scrolled past
A page fires in PagerDuty and the on call engineer has not acknowledged it inside the window. Rather than sending another notification into the same stream that was already ignored, the agent rings the operations bell, which sounds on the screen in the ops room and on every subscribed phone with a sound reserved for exactly this. Because it is reserved for exactly this, the sound still works. The agent's job is as much about not ringing as about ringing.
One flow, several floors
A company runs three teams that each want their own bell: sales, support, and the fundraising campaign. The flow does not hardcode identifiers. It calls List PingBells, matches the bell by name against the team the event belongs to, and rings that one. When a fourth team gets a bell, they create it in the app and name it to the convention, and the existing flow finds it. A booking confirmed in Calendly rings the sales bell; a milestone on the campaign rings the campaign bell.
Human-in-Loop Highlight
There is no way to un-ring a bell, and there is a worse irreversibility underneath that one: a bell that fires for things that do not matter stops working, permanently, and no configuration change brings back the reflex it trained out of people. The attention this connector spends cannot be refunded. That is why the gate here sits on the rule rather than on any individual ring.
When an agent finds a pattern its current rule does not cover, a renewal that is technically an order, a support escalation that resolved itself twice last week, a threshold it could lower to catch more wins, it does not start ringing. It holds and asks: "Renewals over the threshold are matching the sales bell rule, but the rule was written for new business. Adding them would have rung the sales bell more times last week than the new business rule did. Add renewals to the sales bell, give them their own bell, or leave them in the channel only?" The floor lead answers on the channel FlowRunner is listening on, and the rule changes only if a person changed it. The agent can ring the bell all day. What the bell is for belongs to the people who have to hear it.
Agent Capabilities
2 actionsRinging
2- Ring PingBell Posts an event to a single PingBell, which increments its live counter on every paired screen and sends a push notification with that PingBell's own sound to every subscribed teammate. The wording and the sound live in the PingBell app rather than in the flow, so this action takes only the bell's identifier. Used for wins, milestones, and escalations that need the room to look up rather than to read something.
- List PingBells Retrieves every PingBell on the authenticated account with its identifier and name. Used to resolve a bell by name at run time so one flow can serve several teams, and so a new bell created in the app is picked up without editing the flow.
Frequently Asked Questions
What can FlowRunner do with PingBell?
FlowRunner agents can run Ring PingBell and List PingBells in PingBell.
Does connecting PingBell to FlowRunner require OAuth?
No. PingBell connects to FlowRunner with an API key, no OAuth flow required.
Can PingBell trigger a FlowRunner workflow automatically?
PingBell doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PingBell
$100 in credits. No card required. Connect in minutes.