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.
How do Loop Flows work?
When Conditions
What are IF conditions
What are actions (THEN)
Use cases of Loop Flows
Help Section
This guide walks you through the different configurations available on Loop flows and the use cases. Loop flows are built on the fundamental logic of When, If, and Then.
To set up a flow, go to Loop Admin, select Flows, and then choose Create Flow.
Here’s a concise explanation of the options available for configuring a flow in Loop using the specified logics.
This condition specifies when the “IF condition” should be activated/executed and has four options.
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 gets failed.
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.
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.
Payment-based Conditions:
Payment failure message: Set conditions based on specific messages received during payment failures.
Payment failure code: Trigger actions based on certain codes returned from payment gateways during transaction failures.
Available retry count: Configure actions based on the number of retry attempts left for a payment.
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: Set up actions based on the geographic location of the customer.
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:
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.
Change subscription plan: Modify the subscription plan for a customer.
Product-based Actions:
Add one-time product: Include a one-time product to a customer's existing order or subscription.
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 behaviors or attributes.
Remove customer tag: Remove an existing tag from a customer profile.
Bundle-based Actions:
Split bundle into individual items: Break down a bundled product into its individual components within a subscription.
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.
There is no need to worry. We are here to assist you. Please contact us at support@loopwork.co or feel free to reach out to us through the chat by clicking on the support beacon located at the bottom right corner.
Regards,
Loop Subscription Team 🙂
Content of the article:
How do Loop Flows work?
When Conditions
What are IF conditions
What are actions (THEN)
Use cases of Loop Flows
Help Section
How do Loop Flows work?
This guide walks you through the different configurations available on Loop flows and the use cases. Loop flows are built on the fundamental logic of When, If, and Then.
Let's understand about When, If, & Then conditions:
To set up a flow, go to Loop Admin, select Flows, and then choose Create Flow.
Here’s a concise explanation of the options available for configuring a flow in Loop using the specified logics.
When Conditions
This condition specifies when the “IF condition” should be activated/executed and has four options.
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 gets failed.
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.
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.
Payment-based Conditions:
Payment failure message: Set conditions based on specific messages received during payment failures.
Payment failure code: Trigger actions based on certain codes returned from payment gateways during transaction failures.
Available retry count: Configure actions based on the number of retry attempts left for a payment.
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: Set up actions based on the geographic location of the customer.
What are actions THEN
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:
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.
Change subscription plan: Modify the subscription plan for a customer.
Product-based Actions:
Add one-time product: Include a one-time product to a customer's existing order or subscription.
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 behaviors or attributes.
Remove customer tag: Remove an existing tag from a customer profile.
Bundle-based Actions:
Split bundle into individual items: Break down a bundled product into its individual components within a subscription.
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. |
Need help?
There is no need to worry. We are here to assist you. Please contact us at support@loopwork.co or feel free to reach out to us through the chat by clicking on the support beacon located at the bottom right corner.
Regards,
Loop Subscription Team 🙂
Updated on: 19/09/2024
Thank you!