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.

HubSpot triggers are a type of service trigger: they fire based on events happening inside a connected HubSpot account. For example, a deal moving to "Closed Won," a new contact being created, or a support ticket's priority changing. Once you've connected HubSpot, you choose the object and event you care about, optionally narrow it down with filters, and tell Fugo what to show and where.

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

To connect HubSpot, you'll need access to the HubSpot account you want to connect and permission to approve the OAuth scopes Fugo requests during setup.

HubSpot is connected once, at the account level, and that single connection can power both HubSpot triggers and HubSpot dashboards in Fugo - you don't need to reconnect separately for each.

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 Add new connections, find HubSpot and click Add.

5. A popup window opens for you to log into HubSpot and approve the requested scopes. Choose the HubSpot account you want to connect, then work through HubSpot's consent screen.

6. Once you close the popup (or it closes on its own after you finish), Fugo detects the new connection automatically and shows a confirmation that HubSpot connected successfully.

Your connection now appears under My connections with a status indicator - green means connected, red means the connection has failed and needs reconnecting.

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

2. This opens the trigger builder's Trigger 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 HubSpot 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 HubSpot card. This opens the HubSpot Configuration panel, where you'll set up your object, action, and filters.

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

At the top of the HubSpot Configuration panel are two dropdowns:

Choose which HubSpot object type you want Fugo to monitor: Deal, Contact, Company, or Ticket. This determines which properties are available to filter on further down, so configure this first.

Choose which kind of change should count as the event: Created, Updated (any property on the object changes), Deleted, or Any (fires on all three).

Changing the Object automatically adjusts the Action options to match - for example, switching from Deal to Ticket resets a specific action like "Created" to the equivalent Ticket action, while "Any" carries over as-is since it applies regardless of object type.

A new trigger starts out preselected to Deal / Created so the panel isn't empty - change either dropdown to whatever fits your use case.

Filters narrow down which specific events should count, based on the properties and values in your connected HubSpot account. 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:

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

Here's what that looks like in practice, for a trigger tracking high-value deals closed by a specific rep:

This trigger is set to Deal / Updated, with three filters joined by AND:

Because every condition has to be true at once, this trigger only fires when a deal is Sarah's, worth $10,000 or more, and specifically reaches Closed Won in the Active Sales pipeline - a $15,000 deal owned by someone else, or one of Sarah's deals moving to a different stage, won't set it off.

Deals and Tickets get a special combined filter row for Pipeline and Stage, since HubSpot ties deal/ticket stages to a specific pipeline.

Picking a specific pipeline scopes the Stage dropdown to just that pipeline's stages.

Picking Any pipeline instead switches Stage to a deduplicated list of stage names across all your pipelines - handy if you have several pipelines that all include a stage like "Closed Won" and you don't want to build a separate filter for each one.

If you'd rather describe your trigger in plain language than pick through dropdowns, click Use AI suggestion at the top of the panel.

Type what you want in plain English - for example, "fire when Sarah Donahoo closes a deal of $10,000 or more" - and click Suggest:

Fugo reads your actual HubSpot schema (the real property names, pipelines, and stages in your connected portal) and proposes a matching Object, Action, and set of structured filters, which it drops straight into the fields above for you to review. Nothing is saved automatically - the suggestion is advisory, and you can edit or discard any part of it before clicking Save:

That prompt would come back very close to the filter set built by hand above: Deal / Updated, with Deal owner equals Sarah Donahoo and Amount at least 10000 pre-filled:

The one thing it can't reliably infer from that wording alone is which pipeline counts as "closes" - a portal with more than one pipeline may have a Closed Won stage in each, so the suggestion might match any pipeline with that stage name rather than the specific Active Sales Pipeline used in this example.

If your prompt can't be confidently mapped - because it's too vague, references a property that doesn't exist in your portal, or names a stage that's ambiguous across multiple pipelines - you'll see a warning or error banner explaining what to fix instead of a silently wrong suggestion. Dismiss the banner with the X once you've addressed it.

The AI suggestion tool works best when your prompt maps cleanly onto real HubSpot data:

Once you've saved your trigger settings, you'll see them listed in the trigger details panel to the right. Click Next to move onto 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

You might choose a pre-configured image or video to play - for this example, we'll select an existing Media item: a "Closed Won" slide for Sarah

Your chosen content will be added to the content list on the right, where you can configure its settings (click the cog icon):

HubSpot and Salesforce triggers get one additional option not available elsewhere: Message, a dynamic text slide that fills in details from the event that fired it. This is what lets a single template announce every matching deal or ticket with the right name and amount, instead of you building a new slide by hand for each outcome.

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 — for example, choosing "Deal Owner" inserts {hubspot_owner_id} at your cursor. Placeholders pull from the same property 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").

How long the message stays on screen, set in milliseconds.

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 criteria configured, display content chosen, and at least one screen target set. You can review your trigger conditions before saving and publishing in the Preview step:

Once published, your trigger is listed as On Standby on the Triggers page - active and waiting for its condition(s) to be met:

If you edit a published trigger afterward without republishing, it's flagged Outdated until you publish the new version.

Before relying on a new trigger, it's worth confirming it fires the way you expect. Create the conditions in HubSpot that match your filters - for example, if your trigger fires when a deal over $10,000 closes, create or update a test deal that meets that criteria - and confirm the right content appears on your screen.

If something isn't working as expected, you're not seeing the HubSpot properties 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