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 - no one has to remember to switch anything back.

Use triggers to:

Conceptually, a trigger is really just a playlist with a rule attached that decides when it should play. That's why triggers use the same permissions and the same content-picking flow as playlists elsewhere in Fugo. You're not learning a second system, just a new way to decide the timing of a playlist you already know how to build.

Triggers use the same permissions as playlists - create, edit, and publish - rather than a separate "trigger" permission.

This follows from triggers being playlists with a firing rule attached: if someone already has permission to publish playlists, they have what they need to build and run triggers too.

Log into your account (or start a 14-day free trial), then go to Triggers from the left-hand navigation. This opens your trigger library - every trigger your team has created, in either a Grid or List view (Fugo remembers whichever you used last).

A toolbar above the list lets you find and organize triggers as the list grows:

Each trigger shows a preview of its content, its name, its type (Manual, Timer, HubSpot, or Salesforce) and a screen count, plus a status badge so you can tell what's going on at a glance:

In List view, manual triggers get their Play Once and Loop controls right in the row, so you can fire or stop one without opening it:

Select multiple triggers using their checkboxes to bulk delete, duplicate, publish, or unpublish them together. Click into any single trigger to open its detail panel, where you can edit, duplicate, or delete it (delete asks for confirmation first) - the same quick actions as a bulk selection, just for one trigger at a time.

You'll create a new trigger from the Triggers page by clicking New Trigger:

Creating a new trigger will open the trigger builder.

Fugo currently supports three trigger types. Each one is a different way of telling Fugo when to fire a playlist.

Manual triggers let you fire a playlist yourself, on demand, with a single click. They're the right choice whenever the "when" isn't something you can schedule in advance - a spontaneous announcement, an all-hands takeover, or anything you want on screen right now.

In this example trigger, I've set up a welcome message I can fire when my visiting client arrives on site:

You can run a manual trigger two ways, depending on how long you need the content to stay up:

Plays your chosen content a single time, then automatically returns to your normal schedule. Use this for a one-off message that doesn't need anyone to remember to turn it off.

Plays your chosen content continuously until you stop it. Use this for something that should stay up indefinitely - during an event, for example - where you'll actively decide when it's over rather than let a timer decide for you.

Either way, once a manual trigger is running you can stop it early at any time. It isn't a fire-and-forget action, so a Play Once you started by mistake or a Loop you're ready to end is always one click away from stopping.

To fire off your manual trigger, you need to click either "Play once" or "Loop" on it's preview card.

In grid view, select the trigger card and use the buttons in the preview panel:

In list view, use the buttons that are fixed within the trigger's tile:

Timer triggers fire a playlist automatically at a specific date and time you set without any manual activation. They're the right fit whenever you already know exactly when you want content to appear, like a recurring stand-up slide or a promotion that starts on a specific morning.

You'll set a start date and time (required). You can optionally set an end date and time; if you don't, your content plays through once and your screens return to normal automatically - you're not required to define an end point just to use a timer trigger:

In this example trigger, I've set it up to fire off 15 minutes before Friday's all hands meeting on every screen in my screen network that's tagged with the "staff-facing" property:

There's currently no dedicated stop button for a timer trigger, since - unlike a manual trigger - it's designed to run unattended on a schedule you already set.

To stop or reschedule one before it fires, open it and edit the date/time, or delete it entirely.

Service triggers fire a playlist automatically based on events happening in a tool you've connected to Fugo, so your screens can react to things happening in the systems your team already works in without anyone needing to remember to post an update manually.

Once connected, you choose the object and event you care about - for example, a deal being marked "Closed Won" - and Fugo listens for that event and fires the matching playlist in real time.

Fugo currently supports service triggers for:

For both, you can build your trigger conditions two ways:

In this example trigger, I've set it up to fire off whenever our sales rep Nick marks a $50K+ a deal as closed in HubSpot:

Whichever trigger type you use, you'll choose what shows on screen when it fires. Most of these options are the same content types you'd choose from anywhere else in Fugo, so nothing here is trigger-specific to relearn.

An image, video, audio, or presentation file from your media library - the same library used for regular playlists.

A slide or slideshow built in the Design Studio, useful when you want the trigger's content to match your existing brand templates rather than a plain file.

A dashboard connected through Fugo's TV Dashboards feature - handy for a service trigger that should surface a live report the moment a relevant event happens, rather than a static slide.

Available only for HubSpot and Salesforce service triggers, this is a dynamic text slide that automatically fills in details from the event that fired it - so a single Message template can announce every "Closed Won" deal with the right name and amount, rather than you having to build a new slide for each possible outcome.

Once you've set up your trigger conditions and chosen what content will play when the conditions have been met, you need to choose where this content will show.

You'll do that in the Screens step of the trigger builder.

You can target screens two ways:

This lets you pick individual screens or screen Groups directly - the same picker used elsewhere in Fugo, with search built in so you can find what you need in a large screen list.

This lets you target dynamically instead: rather than naming specific screens, you set a condition on one of your custom screen properties (for example, Region = East, or Store Type = Flagship), and any screen matching that condition is targeted automatically - including screens you add later that happen to match. This is especially useful for larger deployments, where you'd rather maintain targeting rules than update a screen list by hand every time your fleet changes.

Switching between By Screen and By Property clears whatever you'd already selected in the other mode, so it's worth deciding up front which approach fits your trigger before filling it in.

Both modes support selecting multiple targets - several screens and Groups, or several property conditions - so a single trigger can fire across as many displays as you need.

Publishing works the same way here as it does with playlists: a trigger can be saved as a draft at any point, but going live requires Save and Publish, which stays disabled until the trigger has content, a screen target (direct or property-matched), and its firing conditions all configured.

Once published, the trigger is active and will fire on its assigned screens whenever its conditions are met. You'll see it labled as On Standby:

Want Fugo to support another connector? Not seeing the properties you'd like to filter for? Trigger not firing as expected?

Reach out through the chat box in the Fugo CMS or email us at support@fugo.ai -we're happy to help.