A FUGO whitepaper for Salesforce administrators and revenue operations teams
Summary
Most teams already have the data they need. What they lack is a moment where everyone sees the same thing at the same time.
Salesforce reports and dashboards are excellent for the person who opens them. They are much weaker at reaching the person walking past, the team standing up for a huddle, or the floor that has no reason to log in at all. Screens in offices tend to show either nothing, or a dashboard someone configured months ago that no longer reflects what matters this quarter.
FUGO TRIGGERS takes a different approach. Instead of displaying a dashboard on a loop, it reacts to change. When a record in Salesforce changes in a way you care about, Salesforce pushes that change to FUGO, and FUGO publishes content to the screens you choose — within seconds, without anyone refreshing anything.
This paper explains what that makes possible, how it works, and what it requires.
The problem with dashboards on screens
Putting a Salesforce dashboard on an office television is the obvious move, and it disappoints for predictable reasons.
It ages. A dashboard pinned to a screen reflects the priorities of whoever set it up. Six months later it is furniture. Nobody owns it, nobody notices it is stale, and nobody wants to be the person who asks for a login to change it.
It is the same at 9am and 4pm. A dashboard shows state, not events. It cannot distinguish an ordinary Tuesday from the moment a deal your team has worked for eight months finally closes. Everything gets equal visual weight, so nothing has any.
It demands attention rather than earning it. Reading a dashboard is work. Someone has to stop, look, interpret, and care. That happens on day one and rarely afterwards.
It needs a session. A screen showing Salesforce needs a logged-in browser somewhere, which means a shared account, a password that expires, and a session that drops at the worst possible moment.
The underlying issue is that a dashboard answers "what is the current state?" when the question a room actually responds to is "what just happened?"
What changes when signage becomes event-driven
FUGO TRIGGERS watches for changes to Salesforce records and publishes content in response. A few examples of what teams build with it:
Celebrate closed business as it happens. An Opportunity moves to Closed Won above a threshold you set, and a celebration slide appears across the sales floor with the account name, the value, and the rep who closed it. The moment is shared while it is still a moment.
Make service levels visible. A Case breaches its SLA, or the open-case count crosses a line, and the support floor sees it without anyone raising an alarm.
Welcome people properly. A meeting or visit recorded in Salesforce puts a named welcome on the reception screen at the right time.
Show pipeline movement, not pipeline totals. A large deal entering a late stage is a more useful signal than a running total that barely moves day to day.
Recognise the team. New logos, first deals, anniversaries — anything represented as a record change can become something the room sees.
The common thread is that these are events. They have a moment, and that moment is what makes them worth showing. A dashboard cannot express them; a trigger can.
How it works
FUGO TRIGGERS is an integration, not an app that runs inside Salesforce. The managed package you install contains no code — no Apex, no Lightning Web Components, no Visualforce. It contains an External Client App and its OAuth settings, which is how Salesforce recognises FUGO as an authorised client. Everything else happens in FUGO.
1. Install and connect. An administrator installs the managed package, then connects from FUGO using standard OAuth. FUGO requests only two permissions: the ability to read data through the API, and the ability to keep the connection alive.
2. Choose what to watch. You pick the objects that matter — Opportunity, Case, Account, or a custom object. FUGO enables Salesforce Change Data Capture for those objects on your behalf.
3. Salesforce pushes changes to FUGO. FUGO subscribes to the Salesforce Pub/Sub API. When a watched record changes, Salesforce delivers the change to FUGO directly. Nothing polls, nothing runs on a schedule, and nothing waits for the next refresh interval.
4. Your rules decide what matters. Not every change should interrupt a room. You define the conditions — stage, amount, owner, priority, whatever the object supports — and only matching changes proceed.
5. Content reaches the screens. FUGO builds the content and publishes it to the screens you targeted. Existing playlists resume afterwards.
Why event-driven matters
Integrations that poll ask "has anything changed?" on a timer. That approach is slow by design, and gets slower as it is asked to watch more. It also wastes API capacity asking questions whose answer is usually "no".
Change Data Capture inverts this. Salesforce already knows the instant a record changes, and tells FUGO. The result is faster, quieter on your org's API limits, and — importantly for anything meant to feel live — actually live.
Security and data handling
Signage is a public surface. What appears on a screen in a lobby is visible to everyone who walks past, so the questions of what FUGO can see and what it keeps deserve direct answers.
Least privilege by design. The app requests two OAuth scopes: Api and RefreshToken. It cannot act as you in the Salesforce user interface, and it holds no broader access than reading through the API.
Modern authorisation. Connections use OAuth 2.0 with PKCE (S256) enforced. Refresh tokens rotate, and expire after 30 days of inactivity. These controls are locked on the app and cannot be weakened.
Fixed network origin. Salesforce will only accept token requests from FUGO's registered static addresses. A token taken from anywhere else is refused.
FUGO writes almost nothing. The integration reads. The single exception is enabling or disabling Change Data Capture for an object when you ask for it, which is a configuration change on the channel and never touches business records. Because it modifies org configuration, the connecting user needs the Customize Application permission.
Data is processed, not warehoused. Change events and the records referenced by them are processed in memory to build content. FUGO stores no copy of your Salesforce database. Where you deliberately place Salesforce fields into a slide, those values are stored as part of that content — because they are the content.
Encryption throughout. All traffic uses TLS 1.2 or higher. Stored access and refresh tokens are encrypted at rest.
You remain in control. Access can be revoked at any time from Setup → Connected Apps OAuth Usage, and Change Data Capture can be switched off per object independently.
What you need
| Salesforce edition | Any edition supporting Change Data Capture and the Pub/Sub API |
| Permissions to connect | A Salesforce administrator. Customize Application is required to enable CDC |
| Installed components | One External Client App and its OAuth settings. No Apex, LWC, Aura or Visualforce |
| FUGO account | With screens already paired |
| Screens | Any hardware FUGO supports — smart displays, media players, or a browser |
Installation is a standard managed-package install, typically for administrators only.
Things worth knowing before you start
Change Data Capture has org-level limits. Salesforce caps how many objects can be enabled for CDC and how many events an org receives. Both are generous for signage, but worth checking if you already use CDC for other integrations.
Not every field arrives in a change event. A CDC event carries the fields that changed. Where a trigger needs related context — an owner's name, an account's industry — FUGO fetches the referenced record, visible only to the connecting user's permissions.
Design for a glance. The most common mistake is treating a screen like a report. People walking past give a screen a second or two. One idea per slide, legible from across the room, beats a dense layout every time.
Decide what deserves interruption. Everything can be a trigger. Very little should be. The screens that keep working are the ones showing things a room genuinely wants to know, which usually means fewer triggers with tighter conditions.
About FUGO
FUGO is a digital signage platform for managing screens and the content on them, from one place, at any scale. FUGO TRIGGERS extends that to Salesforce, so the things your team cares about can leave the CRM and reach the room.
Learn more: fugo.ai · Support: support@fugo.ai
