Skip to main content
As your launches grow, you will have dozens of flows running across multiple campaigns. The Active Triggers Overview gives you a single view of every trigger that is currently turned on — across all your launches, all your stages, and all your flows. No more hopping between launches to check what is active.

Where to Find It

Navigate to the Launches page and look for the Active Triggers Overview section. It sits above your launch cards, giving you a high-level snapshot before you dive into individual launches.

The Dashboard at a Glance

At the top of the Active Triggers Overview, you will see two key numbers:
  • Total Active Triggers: The count of all triggers currently turned on across every launch
  • Conflict Count: The number of trigger conflicts detected (more on this in Trigger Conflicts)
A conflict count of zero means you are in the clear. Any number above zero deserves your attention — it means two or more flows might fire simultaneously for the same fan action.

How Triggers Are Organized

Active triggers are grouped by activity type, making it easy to scan what is listening for what. Groups include:
GroupTriggers Inside
PresaveFan pre-saves your music
StreamFan streams your music, Fan clicks streaming link
RSVPFan RSVPs to an event
TicketFan clicks a ticket link
PurchaseFan purchases merch, Fan clicks merch link
EmailFan opens an email, Fan clicks an email link
SMSFan replies to SMS, Fan opts in to SMS
Instagram DMFan sends IG DM (keyword match)
Instagram CommentFan comments on post, reel, or live
Instagram StoryFan mentions you in story, Fan replies to your story
ListFan joins a list
ExtraFan joins an extra
Sign-upFan signs up (new fan)
Each group expands to show the individual trigger rows inside it.

What Each Trigger Row Shows

Click on a trigger group to expand it. Each row inside represents one active trigger and displays:
  • Flow Name: The name of the flow this trigger belongs to
  • Launch Name: Which launch the flow is part of
  • Cycle Stage Badge: A color-coded badge (purple for Pre-Release, orange for Release, pink for Post-Release)
  • Campaign Asset Name: If the launch is a multi-asset campaign, which specific asset this flow targets
  • Inline Toggle Switch: An on/off switch to enable or disable this specific flow directly from this view
  • Open Flow Link: A quick link that takes you directly to the flow in the Flow Builder

Filter Modes

Use the filter tabs at the top of the Active Triggers Overview to narrow your view:

All

Shows every active trigger across all launches. This is your default view and the best place to get the full picture.

Conflicts Only

Shows only trigger groups where two or more flows share the same trigger definition. Use this when you need to quickly find and resolve conflicts before they cause duplicate messages.

No Conflicts

Shows only trigger groups with a single flow — no competition, no risk of duplicates. These are your “safe” triggers. The search bar lets you find triggers quickly by typing:
  • A flow name — Find all triggers belonging to a specific flow
  • A launch name — Find all triggers belonging to a specific launch
  • A trigger name — Find all triggers of a specific type (e.g., “presave”)
Search works across all three filter modes and updates results in real time as you type.

Inline Toggling

One of the most powerful features of the Active Triggers Overview is the ability to toggle flows on and off directly from this view. No need to open the launch, find the flow, navigate to the flow detail page, and flip the switch there. Just click the toggle switch on any trigger row to:
  • Turn off a flow that is causing conflicts or sending messages you want to pause
  • Turn on a flow that is ready to go live
The toggle takes effect immediately. When you turn off a flow, its trigger stops listening for events. Fans already in the flow will continue their journey, but no new enrollments will happen.
Tip: After toggling, switch to the “All” filter to verify your changes look correct across the full trigger list.

Reading the Overview Effectively

Here is a workflow for using the Active Triggers Overview:

Daily Check (30 seconds)

  1. Glance at the total active triggers count — does the number match what you expect?
  2. Check the conflict count — is it zero? If not, investigate.

Before Activating a New Flow (1 minute)

  1. Open Active Triggers Overview
  2. Search for the trigger type you are about to activate (e.g., “presave”)
  3. Check if any other flows already use that trigger
  4. If conflicts would arise, decide which flow to keep active
  5. Go activate your new flow

Weekly Audit (5 minutes)

  1. Switch to “All” filter and scroll through every active trigger
  2. Are there flows that should have been turned off by now?
  3. Are there triggers from completed launches still running?
  4. Clean up any stale triggers by toggling them off

Use Cases

”What is actually running right now?”

You just came back from vacation and need to know the state of your automations. Open Active Triggers Overview, scan the list, and in 30 seconds you know exactly what is active.

”Why did a fan get two DMs?”

A fan tells you they received two Instagram DMs. Open Active Triggers Overview, filter to “Conflicts,” and check the Instagram DM group. You will likely see two flows with overlapping keyword triggers. Toggle off the one you do not need.

”Is it safe to turn on this new flow?”

Before activating a new presave flow for your upcoming single, check the overview. If another presave flow from a previous launch is still active, you can turn it off first to avoid confusion.

Tips and Best Practices

  • Make it a habit: Check the Active Triggers Overview every time you visit the Launches page
  • Zero conflicts is the goal: Resolve conflicts proactively, not after fans complain about duplicate messages
  • Turn off flows from completed launches: Just because a launch is over does not mean its flows automatically deactivate — clean up manually
  • Use search before activation: A quick search takes 5 seconds and can save you from embarrassing duplicate messages
  • Combine with Execution Logs: If you see a conflict, check the Execution Logs on the affected flows to see if duplicate messages were actually sent

What Happens Next

If you spot conflicts in the Active Triggers Overview, you will need to resolve them. Learn exactly how in Trigger Conflicts.