What Are Flows?
A flow is an automation workflow. It starts with a trigger (something a fan does), followed by a sequence of actions (things you do in response), connected by delays and conditions. Here is a simple example:The Visual Canvas
The Flow Builder uses a ReactFlow-powered drag-and-drop canvas. Each step in your flow appears as a node on the canvas, connected by lines (edges) that show the order of execution.Node Types
| Node | Shape | Purpose |
|---|---|---|
| Trigger | Rounded rectangle | The event that starts the flow |
| Action | Rectangle | Something you do (send email, send SMS, etc.) |
| Delay | Rectangle with clock icon | A pause before the next step |
| Condition | Diamond | A Yes/No branch based on criteria |
Canvas Controls
- Zoom: Scroll to zoom in and out, or use the zoom controls in the bottom-left corner
- Pan: Click and drag on empty canvas space to move around
- Select: Click any node to select it and view its settings
- Connect: Drag from a node’s output handle to create a new connection
- Delete: Select a node or edge and press Delete/Backspace
- Undo/Redo: Standard keyboard shortcuts work on the canvas
Flow Structure
Every flow follows a consistent structure:1. Trigger (Required)
The trigger is always the first node. It defines what fan action starts this flow. Examples include a fan presaving your music, sending an Instagram DM, replying to an SMS, purchasing merch, and more. A flow can have one trigger or no trigger (triggerless flows are entered only via Go-to-Flow from another flow).2. Actions
Actions are the things that happen in response to the trigger. Send an email, send an SMS, send an Instagram DM, add the fan to a list, tag their profile, or redirect them to another flow. Actions execute in sequence — one after the other, top to bottom.3. Delays
Delays create pauses between actions. Wait 2 hours before the follow-up. Wait until release day. Wait for the fan to open your email. Delays are crucial for building natural-feeling sequences that do not bombard fans with everything at once.4. Conditions
Conditions create branches — Yes/No splits based on criteria. “Did the fan presave?” “Is the fan a VIP?” “Did they open the last email?” Each branch can continue with its own actions, delays, and even more conditions. This is where flows get powerful — you can create different experiences for different fan behaviors.Where Flows Live
Flows belong to launches and are assigned to a specific cycle stage (Pre-Release, Release, or Post-Release). On the launch detail page, you will see flows organized under their respective stage sections. Quick Automations — standalone flows not tied to a launch — live under the Automations tab on the Launches page.Flow Chaining with Go-to-Flow
Flows do not have to be standalone. The Go-to-Flow action lets you redirect a fan from one flow into another. This is incredibly useful for:- Modular design: Build reusable flows (like a “welcome sequence”) that multiple triggers can feed into
- Complex journeys: Split a long sequence into manageable chunks
- Cross-stage transitions: Move a fan from a Pre-Release flow into a Release flow when the time comes
Real-Time Execution
When a fan triggers a flow, Fanaura executes it in real time using a reliable message queue. This means:- Guaranteed delivery: Messages are queued and retried if delivery fails
- Scalable: Thousands of fans can trigger flows simultaneously without bottlenecks
- Reliable delays: Time-based delays are handled by the message queue, so they fire exactly when scheduled — even if Fanaura is processing other tasks
The Three Tabs
Every flow detail page has three tabs:Canvas
This is the visual builder where you design your flow. Add triggers, actions, delays, and conditions. Connect them together. This is where you spend most of your time.Settings
Configure flow behavior: enrollment rules, timezone settings, time windows for sending, communication defaults. See Flow Settings for details.Enrollment
View every fan who has entered this flow, their current status, and where they are in the journey. See Enrollment History for details.Execution Logs
Debug your flows by viewing every action that has executed, success/failure status, and error details. See Execution Logs for details.A Simple Flow, Start to Finish
Here is what building a flow looks like in practice:- Navigate to your launch and click “Add Flow” under the Pre-Release stage
- Name it: “Presave Thank You Sequence”
- The canvas opens with an empty workspace
- Click the add button to add a trigger: “Fan pre-saves your music”
- Click the add button below the trigger to add a delay: “Wait 1 minute”
- Add an action: “Send Email” with your thank-you message
- Add another delay: “Wait 3 days”
- Add a condition: “Fan has streamed the song”
- Build out both the Yes and No branches with different follow-up actions
- Toggle the flow active when you are ready
Tips and Best Practices
- Start simple: Your first flow should be a trigger, a delay, and one action. Build complexity from there.
- Test before activating: Use the “Send test” feature in email and SMS actions to verify your messages look right
- Name flows descriptively: “IG DM Presave Responder” is better than “Flow 1”
- Use delays generously: Fans appreciate breathing room between messages. A 1-day delay often outperforms a 1-hour delay.
- Check your conditions: A misconfig in a condition node can send fans down the wrong branch — always double-check the logic
- Monitor Execution Logs: After activating a flow, check the logs within the first few hours to make sure everything is firing correctly