Table of contents

Triggers let your Fugo screens react automatically instead of only following a fixed schedule. When a trigger fires, it plays a chosen playlist on your selected screens for as long as that content runs, then your screens return to their normal rotation on their own.

Salesforce triggers are a type of service trigger: they fire based on changes to records in a connected Salesforce org. For example, an opportunity moving to Closed Won, a new lead coming in from your website, or a case being escalated. Once you've connected Salesforce, you choose the object you care about and which kinds of changes count, optionally narrow it down with filters, and tell Fugo what to show and where.

Behind the scenes, Fugo listens to Salesforce's Change Data Capture stream for the object you pick. Salesforce publishes a change event the moment a record is created, edited, deleted or restored, and Fugo receives it over a live streaming connection rather than checking Salesforce on a timer. That's why Salesforce triggers react within seconds rather than minutes.

Conceptually, a trigger is just a playlist with a firing rule attached. That's why triggers use the same permissions, and the same content and screen-picking flow, as playlists elsewhere in Fugo; you're not learning a second system, just a new way to decide when a playlist plays.

Triggers use the same permissions as playlists (create, edit and publish) rather than a separate "trigger" permission. If you can already build and publish playlists, you have everything you need to build and run triggers too.

Your trigger needs a destination screen to play on. You can pair any supported smart TV or media player. See our full compatibility guide here:

👉 Devices & OS compatible with Fugo

If you don't have hardware yet, you can still build and test triggers using the Fugo Chrome extension player or the Fugo browser player, both of which let you preview playback directly from your browser.

Don't have a Fugo account yet? You can start a 14-day free trial here: www.fugo.ai/app

Connecting Salesforce involves installing the Fugo package into your org and approving Fugo's access, so you'll need a Salesforce administrator to complete the setup (or to sit with you while you do it).

Because Fugo reads change events through Salesforce's APIs, your org needs API access. In practice that means Enterprise, Unlimited, Performance or Developer Edition. The user who connects Fugo needs the API Enabled permission, plus permission to view the records you want to trigger on and to manage Change Data Capture settings (Fugo switches change tracking on for the objects you choose, as described below).

Salesforce is connected once, at the account level, and every Salesforce trigger you build uses that connection. Connecting is a two-part process: first a Salesforce admin installs the Fugo package into your org, then you authorize Fugo to use it.

1. Log into your Fugo account.

2. Click the account icon at the bottom of the left-hand navigation, then choose Settings.

3. Open the Connections tab.

4. Under Not connected, find Salesforce and click Add.

Before Fugo can be authorized, its package needs to be installed in your Salesforce org. The package is what registers Fugo as a trusted app in your org. It's configuration only: it doesn't add any code, objects or page layouts to your Salesforce.

After you click Add, Fugo shows you the package install step first:

1. Click the install link. Salesforce's package installation page opens in a new tab. Log in as a Salesforce admin if you're asked to.

2. When Salesforce asks who to install the package for, choose Install for Admins Only. Only the person connecting Fugo needs access to it, so there's no reason to grant it to your wider team.

3. Click Install and wait for Salesforce to confirm the installation is complete.

4. Return to the Fugo tab and continue to the authorization step.

You only need to install the package once per Salesforce org. If it's already installed, continue straight to Step 2.

1. Continuing from the install step opens a popup window where you log into Salesforce and approve the access Fugo requests. Log in to the org where you just installed the package and work through Salesforce's consent screen.

2. When authorization succeeds, the popup shows a "Salesforce Connected Successfully" message and closes itself after a few seconds. Fugo detects the new connection automatically and confirms that Salesforce connected successfully.

Your connection now appears under My connections with a status indicator: green means Connected, red means Connection failed and it needs reconnecting.

Fugo keeps the connection alive on its own: when Salesforce's access token expires, Fugo refreshes it automatically in the background. You'd only need to reconnect if that refresh fails, for example because the user who connected Fugo was deactivated or had their access revoked in Salesforce.

If you reconnect the same Salesforce org later, Fugo reuses your existing connection instead of creating a duplicate, so the triggers already built on it keep working.

1. Go to Triggers in the left-hand navigation, then click New Trigger.

2. This opens the trigger builder on its Select step, showing every available trigger source as a card: Manual, Timer, and any connected HubSpot or Salesforce accounts. A search, filter and sort toolbar helps you find the right one if you have several connections.

3. If Salesforce isn't connected yet, its card is labeled Not connected. Clicking it takes you straight to the Connections tab covered above rather than letting you select it.

4. Click your connected Salesforce card, then Next. This moves you to the Configure step, where you'll choose your object, the kinds of changes to react to, and any filters.

If you have more than one Salesforce connection, each one appears as its own card (e.g. "Salesforce 1" and "Salesforce 2") so you can build triggers against different orgs.

The Configure step has two tabs: Structured, where you build your conditions step by step, and Prompt, where you describe them in plain English. Most triggers are best built on the Structured tab, which is covered first.

The Structured tab walks you through three questions in order, with a Back button if you want to change an earlier answer.

The first is: Which Salesforce object should trigger this?

Click Select an object… to open a searchable list of the objects in your connected org, grouped into three sections:

Because the list is pulled live from your org, it can be long. Start typing in Search objects… to narrow it down; if there are more matches than fit, Fugo tells you how many are being shown and asks you to refine your search.

When you pick an object, Fugo automatically switches on Change Data Capture for it in your Salesforce org, so there's nothing for you to configure in Salesforce Setup.

Your object choice also determines which fields are available to filter on later, so set this first. Changing the object afterwards clears the change types and filters you'd chosen, since they belong to the old object.

The second question is: When should this trigger? (select all that apply). Choose one or more of the following:

Fires when a new record of this object is created, for example a new lead arriving from a web form. Created events include the full new record, so filters and message placeholders can use any of its fields.

Fires when an existing record is edited, for example an opportunity's stage changing. This is the one to use for "when something moves to…" triggers like celebrating a Closed Won deal.

Fires when a record is deleted (moved to the Salesforce Recycle Bin).

Fires when a deleted record is restored from the Recycle Bin. This is specific to Salesforce, which lets you bring deleted records back.

You can tick as many as you like. If you leave all four unticked, your trigger's summary shows Any, meaning every kind of change to that object counts.

The third question is Property filters (Optional). Filters narrow down which specific changes should count, based on the fields and values in your connected Salesforce org. Without filters, every matching change to the object fires the trigger. Multiple filters are combined with AND: a trigger only fires when every condition you've added is true.

Click Add condition to add a filter row. Each row has three parts:

A searchable dropdown of every field on the object you chose, pulled live from your Salesforce org. That includes custom fields your team has added. Each field is tagged with its Salesforce data type (such as string, currency, picklist or date), which tells you what kind of comparison and value it accepts.

The list also includes fields from related records, shown with an arrow. For example, User → Full Name on an Opportunity is the full name of the opportunity's owner. This lets you filter on something readable, like a rep's name, rather than a Salesforce record ID.

The comparison to apply: equals, does not equal, contains, does not contain, greater than, at least, less than or at most. The options adjust to the field's type: number, currency, percent and date fields offer equals/does not equal plus the four greater/less-than comparisons, while checkbox and picklist fields only offer equals and does not equal.

How you enter this depends on the field type: a searchable dropdown of the active values for a picklist field (such as Stage or Lead Source), True/False for a checkbox, a date or date-and-time picker for date fields, and free text or a number for everything else.

Lookup fields that point at another record expect that record's 18-character Salesforce ID, which is why it's usually easier to filter on a related field like User → Full Name instead.

You can add as many conditions as you need; each new one is joined to the others with an "AND" divider.

Unlike HubSpot, Salesforce doesn't tie stages to separate pipelines in the same way, so there's no special combined pipeline/stage row. To react to a stage, add a condition on the Stage picklist field and pick the stage from its dropdown, just like any other filter.

Here's what that looks like in practice, for a trigger that celebrates a deal being won:

This trigger fires whenever an opportunity is edited and moved into Closed Won. Edits to opportunities in any other stage won't set it off.

If your condition is hard to express with dropdowns, switch to the Prompt tab and describe it in plain English instead, for example "Fire when an opportunity closes as Won". Each time a change comes in for your chosen object, Fugo's AI checks the event against your description and fires the trigger only if it matches.

A few things to keep in mind:

When a prompt is set, your trigger's summary shows Prompt mode configured.

Once you've finished configuring, you'll see your trigger settings summarized in the trigger details panel to the right. Click Next to move on to content selection.

Once your trigger conditions are set, move to the Content step to choose what plays when the trigger fires. This is the same content picker used in the playlist builder, with one additional content option: Message.

Your chosen content is added to the content list on the right, where you can configure its settings by clicking the cog icon.

You might choose a pre-configured image or video to play - for this example, we'll select an existing Media item: a "$50K+ Opportunity won" slide:

HubSpot and Salesforce triggers get one additional option not available elsewhere: Message, a dynamic text slide that fills in details from the Salesforce record that fired it. This is what lets a single template announce every matching deal or case with the right name and amount, instead of you building a new slide by hand for each outcome. It becomes available once you've chosen an object on the Configure step.

To build one, open the Message tab in the content picker and set:

The text that will display, written in a text box.

Click the property selector next to it to insert a placeholder. Placeholders use the Salesforce field's API name in curly braces: choosing the Stage field, for example, inserts {StageName} at your cursor, and fields from related records use a dotted path, such as {Owner.Name} for the record owner's name. Placeholders pull from the same field list used in your filters, and are replaced with the real value from the event when the trigger fires. For example, "New deal: {Name} — {Amount}" becomes "New deal: Acme Corp — 15000".

If a placeholder's field has no value in the event, it's left blank in the message. Remember that Updated events only include the fields that changed, so on Updated triggers, placeholders work best for the fields that changed in that edit. Created triggers have every field available.

How long the message stays on screen, set in milliseconds. It defaults to 10000 (10 seconds) and can be set in steps of one second, with a minimum of one second.

For example:

Click Add message (or Update message if you're editing one) to save it to your trigger's content.

In the Screens step, choose where this content should play. You can target screens two ways:

Switching between By Screen and By Property clears whatever you'd already selected in the other mode, so it's worth deciding which approach fits your trigger before filling it in. Both modes support selecting multiple targets.

Your chosen screens will appear in the screens list to the right.

You can save a trigger as a draft at any point. Going live requires Save and Publish, which stays disabled until your trigger has a source and configuration set, display content chosen, and at least one screen target. You can review your trigger before publishing in the Preview step.

Once published, your trigger is listed as On Standby on the Triggers page: active and waiting for its conditions to be met.

If you edit a published trigger afterward without republishing, it's flagged Outdated until you publish the new version. If the Salesforce connection a trigger uses is removed, the trigger shows a red Not connected badge.

Before relying on a new trigger, it's worth confirming it fires the way you expect. Make a change in Salesforce that matches your conditions (for example, if your trigger fires when an opportunity moves to Closed Won, move a test opportunity into that stage) and confirm the right content appears on your screen within a few seconds.

If you're using a Message, check that every placeholder filled in as expected. A blank placeholder usually means that field wasn't part of the change event (see Updated events above).

This Salesforce error means the authorization step ran before the Fugo package was installed in the org you logged into. Complete Step 1 in that org, then try connecting again. If you have more than one Salesforce org, make sure you install the package and authorize in the same one.

Fugo couldn't refresh its access to Salesforce, which usually means the connecting user's access changed (they were deactivated, lost the API Enabled permission, or Fugo's access was revoked in Salesforce). Reconnect from Settings → Connections with an active admin user. Reconnecting the same org keeps your existing triggers.

Check the following, in order:

If something isn't working as expected, you're not seeing the Salesforce objects or fields you expect, or you'd like to request support for additional CRM events, reach out anytime.

You can contact us through the chat box in the Fugo CMS or email support@fugo.ai, and our team will help you get everything running smoothly.

Don't have a Fugo account yet? Start a 14-day free trial: www.fugo.ai/app