Salesforce × PingBell

Broadcast Salesforce Opportunity stage changes and custom object events to every screen your team has. Connects via Zapier, Make, or Salesforce Flow's outbound webhook.

Connect Salesforce All integrations

Common use cases

Sales floor TV with live deals closed
Closed-Won counter rolled up across multiple orgs
Custom object event broadcasting (service cases, quotes, etc.)
Enterprise multi-team dashboards

What Salesforce + PingBell does together

We don’t ship a native Salesforce Connected App today. What Salesforce has built in is more than enough: Flow Builder’s “Send HTTP request” action, classic outbound messages, and Apex callouts can all POST to PingBell’s webhook endpoint. Zapier and Make have Salesforce modules too if you’d rather not touch Flow.

Either path turns Opportunity stage changes, custom object updates, and Apex-triggered outbound messages into a counter update, team push, and graph point.

Use cases

Enterprise sales teams tracking Closed-Won across global sales floors
Service organizations broadcasting case resolution metrics
Revenue operations rolling up metrics across Sales Cloud and Service Cloud
Field sales teams running regional leaderboards on warehouse/office TVs
Customer Success Operations tracking renewal and expansion

Connection paths

Three options, pick whichever fits your stack:

1. Flow Builder → “Send HTTP request” (most direct). Build a record-triggered Flow on Opportunity (or any custom object), add the HTTP-request action, and POST to your PingBell counter’s webhook URL. Works on Professional and up.

2. Zapier or Make. Both have Salesforce triggers for Opportunity events, custom objects, and reports. Pipe any trigger into an HTTP POST to PingBell.

3. Apex callouts. For high-volume orgs or events that need formula-style transformation before broadcast, an @future Apex method can POST to PingBell. Add the PingBell hostname to your Remote Site Settings first.

Setup

In PingBell, create a counter. Copy its webhook URL.
In Salesforce, build a record-triggered Flow on Opportunity (trigger: stage change to Closed-Won). Add a “Send HTTP request” action with method POST and the PingBell webhook URL.
(Or set up a Zap / Make scenario instead, or write an Apex callout.)
Test the flow with a sample record. Confirm the counter ticks.
Install the PingBell TV and mobile apps. Scan the QR on the TV to pair.

Why PingBell for Salesforce users

Salesforce dashboards live inside the Salesforce UI. PingBell extends them outward: a TV app on the sales floor, push notifications on every rep’s phone, and a counter sound on every Closed-Won. Per-counter pricing — 100-rep floors cost the same as 10-rep teams.

FAQ

Which Salesforce editions work?

The Flow-Builder path works on Professional, Enterprise, Unlimited, and Developer editions. Essentials has limited Flow capability; the Zapier or Make path works on every edition.

Is there a native Connected App?

Not today. The available paths above cover every event type Salesforce can fire, so we haven’t built the OAuth app yet.

Can I broadcast custom object events?

Yes. Any object that supports record-triggered Flow (or has an Apex trigger) can fire to PingBell.

Multi-org setups?

Supported. Configure the Flow / Zap in each org separately; aggregate or split counters in PingBell.

Is there a governor-limit concern with high-volume orgs?

Salesforce treats outbound HTTP requests as callouts subject to standard governor limits. For very high-volume orgs, batch with @future Apex or proxy through Make / Zapier so you don’t hit per-transaction limits.

Connect Salesforce in minutes.

Start the trial, connect Salesforce, and the next event from it will ring a bell.

Start free trial Browse all integrations