Loop flows
Loop flows is a feature that allows you to set up automated actions that are performed based on certain triggers that are configured in Loop. With flows, you can set up automated product swaps at X orders, higher discounts at Y orders, gift products at Z orders, and even a combination of all of these and more to drive up your subscription and improve subscriber retention by gamifying subscriptions.
This guide walks you through the different configurations available on Loop flows and the use cases.
How do Loop flows work?
When conditions
What are IF conditions
What are THEN actions
Reward notifications
Use cases of Loop Flows
Related articles
Need help?
Loop flows are built on the fundamental logic of When, If, and Then.
When is the trigger event on which the flow should start.
If is the condition you can configure for a specific cohort on which the flow should be executed.
Then is the action that defines what should happen when the flow is executed.
To set up a flow, go to Loop Admin, in the Retain section, choose Flows. Click on Create Flow and start configuring the flow settings.
On the flow screen, you can refer to the priority, name, trigger, status, last run time stamp, count of runs and failed in the last 30 days of the flow.
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.
This condition specifies when the “IF condition” should be activated/executed or when the flow should start on any subscription contract. When condition has four trigger events present at the moment.
A new subscription is created: In this case, the IF condition is executed whenever a subscription is created
A recurring order is successfully placed: In this case, the IF condition will be executed when a recurring subscription order is placed by Loop.
When products are modified in a subscription: In this case, the IF condition will be executed when a modification is made at the product level in a subscription.
When the order payment is failed: In this case, the IF condition will be executed when the payment for a subscription order fails.
If conditions in Loop are the same as in programming languages, where the action is activated only if the condition that is preconfigured in the app is met.
In Loop, you can utilize "if" conditions based on various factors such as Subscription, Product, Customer, Payment, Bundle, and Demographic details. Below is an overview of the options available for configuring these conditions:
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.
Order attribute: Trigger action when an order attribute is present.
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.
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.
Total subscription spent: Configure actions when the total spending on 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.
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.
Actions are events that are set to execute when the trigger/IF condition is achieved. The actions that are set up on flows follow the same order of execution as how they are set up on the app.
Subscription-based 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.
Product-based 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.
Customer-based 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-based actions:
Add bundle one-time: Add preset bundle in their upcoming subscription order.
Add bundle as subscription: Add preset 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.
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 allow you to automatically inform customers about the discounts or gifts they’ve earned via banners on the customer portal or by sending emails using 3rd party apps. You can configure these settings at the bottom of each flow.
Available notification options
Send email to customers from Loop: You can send the email using this setting directly via Loop when this flow is executed. Upon enabling it, you will get an option to configure the subject line and HTML-supported email content with variable support.
Publish event to 3rd party apps like Klaviyo: Loop pushes a custom event to third-party marketing platforms such as Klaviyo when this flow is executed. This enables you to create advanced marketing automations specific to the flow that was triggered.
Add reward text in the upcoming order email: Insert custom reward-related information directly into the upcoming order notification email by Loop.
Display reward banner on customer portal: Brands can use this to display banners on the customer portal, showcasing the subscriber's progress and subscription journey. This helps prevent cancellations by keeping subscribers informed and excited about the upcoming rewards and benefits they will receive through active flows.
Loop Flows can be customized in numerous ways to implement a range of actions on subscriptions to meet your specific requirements. The guides for each use case are accessible via the links provided in the table below.
Please note that these use cases are versatile and can be combined in different ways to cater to unique scenarios that may not be directly listed below.
Here are some related articles that may offer additional insight and context.
Subscription discounts
Subscription tags
No worries - we're here for you!
If you have any questions or need assistance, feel free to email us at support@loopwork.co or chat with us using the support beacon at the bottom right of your screen.
Regards,
Loop Subscriptions Team 🙂
Return to top
This guide walks you through the different configurations available on Loop flows and the use cases.
In this article
How do Loop flows work?
When conditions
What are IF conditions
What are THEN actions
Reward notifications
Use cases of Loop Flows
Related articles
Need help?
How do Loop flows work?
Loop flows are built on the fundamental logic of When, If, and Then.
When is the trigger event on which the flow should start.
If is the condition you can configure for a specific cohort on which the flow should be executed.
Then is the action that defines what should happen when the flow is executed.
To set up a flow, go to Loop Admin, in the Retain section, choose Flows. Click on Create Flow and start configuring the flow settings.
On the flow screen, you can refer to the priority, name, trigger, status, last run time stamp, count of runs and failed in the last 30 days of the flow.
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
This condition specifies when the “IF condition” should be activated/executed or when the flow should start on any subscription contract. When condition has four trigger events present at the moment.
A new subscription is created: In this case, the IF condition is executed whenever a subscription is created
A recurring order is successfully placed: In this case, the IF condition will be executed when a recurring subscription order is placed by Loop.
When products are modified in a subscription: In this case, the IF condition will be executed when a modification is made at the product level in a subscription.
When the order payment is failed: In this case, the IF condition will be executed when the payment for a subscription order fails.
What are IF conditions
If conditions in Loop are the same as in programming languages, where the action is activated only if the condition that is preconfigured in the app is met.
In Loop, you can utilize "if" conditions based on various factors such as Subscription, Product, Customer, Payment, Bundle, and Demographic details. Below is an overview of the options available for configuring these conditions:
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.
Order attribute: Trigger action when an order attribute is present.
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.
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.
Total subscription spent: Configure actions when the total spending on 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.
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.
What are THEN actions
Actions are events that are set to execute when the trigger/IF condition is achieved. The actions that are set up on flows follow the same order of execution as how they are set up on the app.
Subscription-based 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.
Product-based 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.
Customer-based 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-based actions:
Add bundle one-time: Add preset bundle in their upcoming subscription order.
Add bundle as subscription: Add preset 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.
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 allow you to automatically inform customers about the discounts or gifts they’ve earned via banners on the customer portal or by sending emails using 3rd party apps. You can configure these settings at the bottom of each flow.
Available notification options
Send email to customers from Loop: You can send the email using this setting directly via Loop when this flow is executed. Upon enabling it, you will get an option to configure the subject line and HTML-supported email content with variable support.
Publish event to 3rd party apps like Klaviyo: Loop pushes a custom event to third-party marketing platforms such as Klaviyo when this flow is executed. This enables you to create advanced marketing automations specific to the flow that was triggered.
Add reward text in the upcoming order email: Insert custom reward-related information directly into the upcoming order notification email by Loop.
Display reward banner on customer portal: Brands can use this to display banners on the customer portal, showcasing the subscriber's progress and subscription journey. This helps prevent cancellations by keeping subscribers informed and excited about the upcoming rewards and benefits they will receive through active flows.
Use cases of Loop flows
Loop Flows can be customized in numerous ways to implement a range of actions on subscriptions to meet your specific requirements. The guides for each use case are accessible via the links provided in the table below.
Please note that these use cases are versatile and can be combined in different ways to cater to unique scenarios that may not be directly listed below.
| Use cases | Support |
|---|---|
| Product swapping | Often used for subscriptions that start with a product combo, such as a coffee machine with beans, transitioning to beans-only from the second order onward. |
| Trial subscriptions | Facilitates swapping a trial or demo product with the main product, commonly utilized to smoothly transition customers from a trial to a full subscription. |
| Add/ Remove product one-time or subscription | Enables the inclusion or removal of products within an ongoing subscription, either on a one-time basis or as a recurring part of the subscription. |
| Discounts after X orders | Automatically applies discounts after a specified number of orders, rewarding recurring customers and enhancing loyalty. |
| Actions based on customer tags | Triggers specific actions based on the presence or absence of customer tags, allowing for targeted marketing and personalized service offerings. |
Related articles
Here are some related articles that may offer additional insight and context.
Subscription discounts
Subscription tags
Need help?
No worries - we're here for you!
If you have any questions or need assistance, feel free to email us at support@loopwork.co or chat with us using the support beacon at the bottom right of your screen.
Regards,
Loop Subscriptions Team 🙂
Return to top
Updated on: 23/06/2025
Thank you!