Skip to main content
Creating a flow is straightforward. In a few clicks, you will have a blank canvas ready for your automation sequence. Here is exactly how to do it.

​
Creating a Flow Inside a Launch

Most flows live inside a launch, assigned to a specific cycle stage. Here is how to create one:

​
Step 1: Navigate to Your Launch

Go to the Launches page and click on the launch you want to add a flow to. This opens the launch detail page.

​
Step 2: Find the Right Cycle Stage

On the launch detail page, you will see sections for each cycle stage:
  • Pre-Release (or Pre-Sale for Tour/Merch launches)
  • Release (or On-Sale)
  • Post-Release (or Post-Sale)
Each section has its own “Add Flow” button.

​
Step 3: Click “Add Flow”

Click the “Add Flow” button for the stage where you want this automation to live. A modal will appear asking you to name your flow.

​
Step 4: Name Your Flow

Give your flow a clear, descriptive name that tells you at a glance what it does. Good examples:
  • “Presave Thank You Email Sequence”
  • “IG DM Keyword Responder — PRESAVE”
  • “Release Day Multi-Channel Blast”
  • “Post-Release Playlist Pitch Follow-Up”
Avoid generic names like “Flow 1” or “Test” — you will lose track of what each flow does as your launch grows.
Tip: Include the channel or trigger type in the name. “SMS Presave Reminder” instantly tells you the channel (SMS) and the purpose (presave reminder).

​
Step 5: Start Building

After naming your flow, you land on the Flow Builder canvas — a blank workspace ready for your first node. The canvas is empty except for a prompt to add your first step. You have two paths from here:
  1. Add a trigger to define what starts this flow (most common)
  2. Skip the trigger if this is a triggerless flow that fans enter only via Go-to-Flow from another flow

​
Adding Your First Trigger

Click the add button (the ”+” icon) on the canvas. A menu appears with all available node types:
  • Trigger — What starts this flow
  • Action — What you do (send email, SMS, etc.)
  • Delay — A pause between steps
  • Condition — A Yes/No branch
Select Trigger to open the trigger selection modal. Browse or search through all available trigger types:
  • Music triggers (presave, stream, click)
  • Tour triggers (RSVP, ticket click)
  • Merch triggers (purchase, cart abandonment)
  • Communication triggers (email open, SMS reply)
  • Instagram triggers (DM, comment, story mention)
  • Other triggers (list join, sign-up, manual enrollment)
Click a trigger to select it. Some triggers have additional configuration — for example, an Instagram DM trigger lets you specify keyword matching rules. Once configured, the trigger node appears on the canvas as the starting point of your flow.

​
Building the Rest of Your Flow

With the trigger in place, continue building by clicking the add button below any node:

​
Adding Actions

Actions are the core of your flow — the messages and operations that happen. Click the add button and select an action type:
  • Send Email — Compose and send an email
  • Send SMS — Send a text message
  • Send Instagram DM — Send a direct message on Instagram
  • Aura Send — AI-personalized multi-channel message
  • Add to List — Add the fan to a specific list
  • Invite to Extra — Invite to exclusive content or events
  • Tag/Update Fan — Modify fan profile data
  • Go to Flow — Redirect to a different flow
Each action opens its own configuration modal. See Actions for details on every type.

​
Adding Delays

Delays create natural pauses in your sequence. Click the add button and select a delay type:
  • Time Delay — Wait a fixed duration (minutes, hours, days)
  • Fan-Action Delay — Wait until the fan takes a specific action
  • Until Date — Wait until a specific calendar date
See Delays for the full breakdown.

​
Adding Conditions

Conditions split your flow into Yes/No branches. Click the add button and select Condition to open the condition builder, where you define the criteria for the split. See Conditions for everything you need to know about branching logic.

​
The Flow Sequence

Nodes execute from top to bottom, following the connecting lines: 
Trigger
  ↓
Delay (Wait 5 minutes)
  ↓
Action (Send Email)
  ↓
Delay (Wait 2 days)
  ↓
Condition (Did they open the email?)
  ├─ Yes → Action (Send SMS follow-up)
  └─ No  → Action (Resend email with new subject line)
Every fan who enters the flow walks through this same sequence, hitting each node in order. Conditions are the only nodes that create parallel paths — fans go left or right based on the criteria.

​
Triggerless Flows

Not every flow needs a trigger. Triggerless flows are entered only when a fan is redirected from another flow via the Go-to-Flow action. This is useful for:
  • Reusable sequences: Build a “Welcome Sequence” flow that multiple triggers feed into
  • Complex journeys: Break a long automation into smaller, manageable flows
  • Conditional routing: Use conditions in one flow to send fans to different triggerless flows based on their behavior
To create a triggerless flow, simply skip adding a trigger and start with your first action or delay.

​
Quick Automations

Quick Automations are standalone flows that are not tied to any launch or cycle stage. They are always-on automations for things like:
  • A welcome email for every new fan who signs up
  • An Instagram DM auto-responder that runs year-round
  • An SMS opt-in confirmation sequence

​
Creating a Quick Automation

  1. Navigate to the Launches page
  2. Click the Automations tab
  3. Click “New Automation”
  4. Name your automation
  5. Build your flow on the canvas — same process as launch flows
Quick Automations appear in the Automations tab and have their own activation toggles, enrollment tracking, and execution logs.

​
Activating Your Flow

After building your flow, it is time to go live:

​
Toggle the Flow Active

In the top-right corner of the flow detail page, you will find the is_active toggle. Flip it to activate the flow. When active:
  • The trigger starts listening for fan events
  • New fans who perform the trigger action are enrolled
  • Actions begin executing for enrolled fans
When inactive:
  • The trigger stops listening
  • No new fans are enrolled
  • Fans already in the flow continue their journey to completion
Important: Before toggling on, check the Active Triggers Overview to make sure your trigger does not conflict with other active flows.

​
Editing an Active Flow

You can edit a flow while it is active, but be aware:
  • Adding new nodes: New nodes will be encountered by fans who have not passed that point yet. Fans who already passed that point in their journey will not go back.
  • Modifying actions: Changes to email content, SMS text, etc. apply to future executions only. Messages already sent cannot be unsent.
  • Removing nodes: Removing a node that fans are currently waiting on (like a delay) may cause those fans to skip to the next step.
When making significant changes to an active flow, consider:
  1. Toggling the flow off
  2. Making your edits
  3. Testing the changes
  4. Toggling back on

​
Tips and Best Practices

  • One trigger per flow: Keep flows focused. If you need the same actions for different triggers, create separate flows or use Go-to-Flow to a shared triggerless flow.
  • Test early and often: Send test emails and SMS messages to yourself before activating
  • Start with simple flows: A trigger, a delay, and one action is a perfectly valid flow. Add complexity only when needed.
  • Use descriptive names: Future-you will appreciate knowing what “IG DM Presave Auto-Reply — Summer Single” does without opening it
  • Build in draft mode: Keep your launch in draft until all flows are ready, then activate everything at once for a coordinated launch

​
What Happens Next

With your flow created, you need to understand the trigger options available to you. Head to Triggers to explore every trigger type.