Flows let you set up automated actions that run based on triggers you configure. You can use them to swap products at a set order count, apply higher discounts after a certain number of orders, add gift products, or combine all of these to create a gamified subscription experience that keeps subscribers engaged and reduces churn.
This guide covers the flow types available, how flows work, and all the configuration options for when, if, and then conditions.
Loop flows are available exclusively on the Loop Pro plan.
Flow types
When you create a flow, you choose from three flow types depending on your use case.
Order journey: Automatically delivers a unique product on every order, turning each order into a fresh, curated experience. Learn more
Rewards journey: Lets you build subscriber reward programs to create delightful experiences at key milestones. Learn more
Create your own workflow: Builds fully customized workflows using all available triggers, conditions, and actions, giving you maximum control. Learn more
To get started, navigate to Loop admin > Retain > Flows, then click Create flow and select a flow type.
How do Loop flows work?
Flows are built on a simple When, If, Then logic.
When is the trigger event that starts the flow.
If is the condition that determines which subscriptions the flow applies to.
Then is the action that runs when the condition is met.
On the flows list screen, you can see the priority, name, trigger, status, last run timestamp, and the run and failure counts for the last 30 days.
Let's understand about When, If, & Then conditions: Here’s a concise explanation of the options available for configuring a flow in Loop using when, if and then conditions.
WHEN conditions
The when condition defines the trigger event that starts the flow for a subscription contract. There are five trigger events available, and you can select multiple triggers on a single flow. This reduces the need to create separate flows for the same use case.
A new subscription is created: The if condition runs whenever a new subscription is created.
A recurring order is successfully placed: The if condition runs when Loop places a recurring subscription order.
When products are modified in a subscription: The if condition runs when a product-level change is made to a subscription.
When discounts are modified in a subscription: The if condition runs when a discount-level change is made to a subscription.
When the order payment fails: The if condition runs when a payment for a subscription order fails.
IF conditions
If conditions work the same way as in programming, where the action only runs when a preconfigured condition is met. You can configure if conditions based on subscription, product, customer, payment, bundle, and demographic details.
Subscription-based conditions
Type of subscription plan: Configure actions based on the specific type of subscription plan a customer has.
Subscription value: Trigger actions based on the monetary value associated with a subscription.
Total specific subscription orders: Activate conditions based on the total number of orders under a specific subscription.
Total specific subscription spent: Trigger actions when the total spending for a specific subscription reaches a set threshold.
Discount code present: Conditionally trigger actions if a discount code is applied to the subscription.
Discount code not present: Trigger actions if no discount code is applied.
Is prepaid subscription: Configure actions to occur if the subscription is prepaid.
Is not prepaid subscription: Trigger actions if the subscription is not prepaid.
Is streak ongoing: Trigger actions if user is enrolled in a streak program.
Is streak not going: Trigger actions if user is not enrolled in a streak program.
Subscription created at: Configure actions based on the subscription acquisition date.
Shipping rate name equals: Trigger actions based on the current shipping rate name.
No discount code present: Trigger actions if no discount code is present on the subscription.
Checkout order date range: Configure actions based on the checkout date range.
Subscription attribute: Trigger actions if the subscription has particular define attribute.
Order attribute: Trigger action when an order attribute is present.
Is cancellation offer applied (any of): Trigger action when a specific cancellation offer is applied.
Note: This condition only supports the product and discount modification triggers in Flows.
Product-based conditions
Products in subscription (any of): Execute actions based on the presence of specific products in a subscription.
Products not in subscription (any of): Trigger actions based on the absence of specific products in a subscription.
Specific collection products present (any of): Activate actions if products from a specific collection are part of the subscription.
Number of products in subscription: Trigger based on the count of products within the subscription.
Weight of products (in grams): Condition actions based on the total weight of the products in the subscription.
Product title: Execute actions based on the title of the product.
Variant title: Trigger actions based on the variant title of the product.
Products in subscription (any of): Execute actions based on the presence of specific products in a subscription.Products in checkout order (any of): Execute actions based on the presence of specific products in checkout order.
Products not in checkout order (any of): Execute actions based on the absence of specific products in checkout order.
Product attribute present: Execute actions based on the presence of specific product level attributes.
Customer-based Conditions
Total customer orders: Trigger actions based on the total number of orders placed by a customer.
Total customer spent: Activate conditions based on the total amount spent by a customer.
Total subscription orders: Use this condition to trigger actions based on the total number of subscription orders a customer has placed.
Loop subscription spent: Configure actions when the total spending on Loop subscriptions by a customer reaches a specified threshold.
Customer tag present: Activate specific workflows if a customer has a certain tag.
Customer tag not present: Trigger actions when a customer does not have a specific tag.
Total customer orders: Trigger actions based on the total number of orders placed by a customer.
Bundle-based Conditions
Bundles in subscription (any of): Activate specific actions if certain bundles are part of the subscription.
Bundles not in subscription (any of): Trigger conditions when certain bundles are not included in a subscription.
Demographic-based Conditions
Country present: Set up actions if the subscription contract has a particular country present.
Country not present: Set up actions if the subscription contract has a particular country not present.
THEN actions
Then actions define what happens when the trigger and if conditions are met. Actions run in the order they are configured in the flow.
Subscription actions
Change subscription plan: Modify the subscription plan for a customer.
Update shipping: Can update manual shipping prices on subscriptions.
Add discount: Automatically apply a discount to a customer’s subscription.
Remove discount: Remove an existing discount from a subscription.
Add trial period: Offer a trial period to a customer's subscription.
Mystery reward: Add a mystery reward as a discount or a gift.
Set next order date: Set the next order date for the subscription based on its checkout order date.
Change subscription status: Set the subscription status as Pause, canceled or expired.
Add or update subscription attribute(s): Add/update a subscription attribute.
Remove subscription attribute: Remove an existing subscription attribute from the subscription.
Product actions
Add one-time product: Include a one-time product in the upcoming subscription order.
Add subscription product: Add a new product to an ongoing subscription.
Remove product one-time: Remove a product for one-time from the upcoming order.
Remove product from subscription: Remove a product from an ongoing subscription.
Remove all products of a collection from subscription: Remove all products belonging to a specific collection from a subscription.
Swap product: Exchange one product for another in the subscription.
Update product attribute: Update the existing product level attributes.
Remove product attribute: Remove the existing product level attributes.
Customer actions
Add customer tag: Tag a customer profile based on certain behaviours or attributes.
Remove customer tag: Remove an existing tag from a customer profile.
Bundle actions
Add bundle one-time: Add preset as well as build your own bundle in their upcoming subscription order.
Add bundle as subscription: Add preset as well as build your own bundle as a subscription product in the subscription.
Remove bundle one-time: Remove a bundle one-time from the upcoming subscription order.
Remove bundle from subscription: Remove bundle from an ongoing subscription.
Split bundle into individual items: Break down a bundled product into its individual components within a subscription.
Order based
Skip order: Skip upcoming order for active subscriptions.
Delay order: Delay upcoming order for active subscriptions.
In the summary tab in Flow, you can set the priority of the flow and can see all the configuration of the flow in one place.
Reward notifications
Reward notifications let you automatically inform customers about discounts or gifts they've earned, either through banners on the customer portal or emails sent via third-party apps. You can configure these at the bottom of each flow.
Available notification options
Send email to customers from Loop: Sends an email directly through Loop when the flow runs. When enabled, you can configure the subject line and HTML-supported email content with variable support.
Publish event to 3rd party apps like Klaviyo: Pushes a custom event to third-party marketing platforms like Klaviyo when the flow runs. This lets you create advanced marketing automations tied to the specific flow that was triggered.
Add reward text in the upcoming order email: Inserts custom reward-related content into the upcoming order notification email from Loop.
Display reward banner on customer portal: Shows banners on the customer portal that highlight subscriber progress and their subscription journey. This keeps subscribers informed and engaged with upcoming rewards, which helps reduce cancellations.
Use cases
Flows can be customized in many ways to handle a range of subscription scenarios. The guides below cover the most common use cases. These can also be combined to handle unique situations not listed here
Use cases | Support |
Often used for subscriptions that start with a product combo, such as a coffee machine with beans, and transition to beans-only from the second order onward. | |
Used to swap a trial or demo product with the main product, helping transition customers from a trial to a full subscription. | |
Add/ Remove product one-time or subscription | Lets you add or remove products from an ongoing subscription, either on a one-time basis or as a recurring change. |
Discounts after X orders | Automatically applies discounts after a set number of orders, rewarding repeat customers and building loyalty. |
Actions based on customer tags | Triggers specific actions based on the presence or absence of customer tags, enabling targeted and personalized workflows. |
FAQs
How to apply a tag automatically when someone is making a purchase?
How to apply a tag automatically when someone is making a purchase?
We can create a flow with the condition "A new subscription is created" and "product in subscription" then add the tag. You can also use the Order tags from Loop > Settings > Subscription Tags.
You can also enable selling plan name tag on orders having subscription items (Both checkout + recurring).
This is useful when merchants run a different operations flow based on the plan purchased by the customer.
Example -> Some merchants run try before buy plans for which the order has a dummy subscription product which needs to be auto-fulfilled since no actual product is being shipped.
In case the order has multiple plan products, then one tag for each unique plan will be added over.
Can I create a flow to modify the first order for the subscription?
Can I create a flow to modify the first order for the subscription?
The first order (which is created at checkout) cannot be modified via Flows as the flow is triggered after the first order is placed. You can modify all the following subscription orders but not the first one.
What is the new “Multiple Flow Triggers” feature
and why is it useful?
What is the new “Multiple Flow Triggers” feature
and why is it useful?
This feature lets you add multiple triggers to a single flow. Previously, you had to create separate flows for each trigger (like “Subscription Created,” “Products Modified,” etc.). Now, you can set all relevant triggers in one flow and define conditions and actions just once.
It saves time and effort. Instead of building and maintaining multiple flows for similar actions, you only manage one. This simplifies your automation, reduces errors, and makes your workflows much more efficient.
Can I set up a customer to start as a semi-annual subscriber and, at the end of that period, automatically migrate to the monthly plan?
Can I set up a customer to start as a semi-annual subscriber and, at the end of that period, automatically migrate to the monthly plan?
Go to your Flows dashboard.
Click Create New Flow.
In the Triggers step, select all the events you want (e.g., “Subscription Created,” “Products Modified,” “Discounts Modified”).
Once selected, you can define conditions (IF) and actions (THEN) as usual.
Save the flow.If you remove a trigger, any conditions that no longer apply will show a warning before being removed. This ensures you don’t lose important logic accidentally.
The flow will execute whenever any of the selected triggers occur, as long as the conditions are met.
Is there a way to have a standard subscription change to a prepaid one using flows?
Is there a way to have a standard subscription change to a prepaid one using flows?
No, currently we cannot convert a standard subscription to a prepaid one using flows.
Need help?
No worries - we're here for you!
If you have any questions or need assistance, feel free to email us at [email protected] or chat with us using the support beacon at the bottom right of your screen.
Regards,
Loop subscriptions team 🙂