Workflows can automate a wide range of subscription experiences, from retention incentives to proactive customer communications. In this article, we'll walk through five recipes you can build and adapt for your own program.
For an introduction to how Workflows are structured, take a look at Getting Started with Workflows.
🛠️ Early Access
Workflows is in Early Access. To request access, fill out the Workflows Interest Form. We're actively building it, so its features and limitations may change without advance notice.
How to use this guide
Each recipe follows the same structure:
- Objective — the business problem the recipe solves.
- When to use this — signals that suggest it's a good fit for your program.
- Customer experience — what your subscribers see from start to finish.
- Setup — the trigger, filters and actions to build.
Recipes are independent. Pick the one that matches what you're trying to do, or read straight through to see what's possible. Recipes marked Template available have a one-click template; for how to use one, see Creating a Workflow from a template. Recipes that send an email need your email provider connected first; see Connecting your email provider.
Most recipes run on their own: you build the Workflow once, and it runs every time a matching event happens in your store. Two use Manual Execution instead, which runs the Workflow once, against a set of records you provide, when you click Execute. Manual Execution is built for one-off bulk changes, like moving a batch of order dates or canceling a group of subscriptions.
Providing data for manual recipes
Manual recipes run against records you provide, either pasted in as raw input or uploaded as a CSV file of up to 1,000 records. The column header must exactly match the record type the action works on, such as order or subscription (not order ID), or the records won't link.
For the full rules, and how to pull the IDs from your reports, see Running a Workflow manually.
Recipes
Template available: This recipe has a one-click template. Click Create Workflow and choose it from the templates, or follow the steps below to build it from scratch and see what each step does.
Objective
Reward subscribers with a free gift at a specific order milestone to reduce drop-off and improve retention.
When to use this
This recipe is a good fit if:
- Your cohort data shows a notable drop in retention between two specific orders (commonly between the second and third order).
- You want to test surprise-and-delight as a retention lever without launching a full loyalty program.
- You have a low-cost product in your catalog that makes sense as a gift.
It's not the right fit if you're trying to acquire new subscribers. Milestone gifts reward existing subscribers, not first-time buyers.
Customer experience
- The customer signs up for a subscription and receives their first few orders as normal.
- When their qualifying order places, the free gift is added automatically.
- The customer receives an email letting them know a gift is on the way.
- The gift arrives in the same shipment as the regular order.
Setup
- Trigger: Recurring Order Placed
- Filter: Successful Order Count equals the number of the order before the one you want to add the gift to. For example, to add the gift to the third order, enter 2. For why, see Which order does an order-count trigger affect?
- Actions:
- Add Gift to Upcoming Purchase
- Send Communication (Klaviyo or Attentive)
Variations
- Trigger on a different order number. Most merchants test a gift on the second order first, but third- or fourth-order milestones can work better, depending on where your retention drops off.
- Use a higher-value gift on a later milestone. Customers who reach their fourth or fifth order have shown strong intent, and a bigger reward can deepen their loyalty.
- Combine with a Klaviyo pre-notification. Send a "you'll get a free gift on your next order" email a few days before the qualifying order places.
Objective
Reward subscribers with a one-time discount at a specific order milestone, as an alternative to a physical gift.
When to use this
This recipe is a good fit if:
- You want to run a milestone reward but don't have a good low-cost gift product available.
- Your margins on the subscribed product allow for a discount without eroding profitability.
- You want to test discount-based retention against gift-based retention to see which performs better for your program. For how, see A/B testing a Workflow.
It's not the right fit if your subscribers are price-sensitive enough to need an ongoing discount. One-time milestone discounts work best as occasional surprise rewards.
Customer experience
- The customer signs up for a subscription and receives their first few orders as normal.
- When their qualifying order places, the one-time discount is applied automatically.
- The customer receives an email letting them know they got a discount on this order.
- The discount appears as a line item on the order confirmation.
Setup
- Trigger: Recurring Order Placed
- Filter: Successful Order Count equals the number of the order before the one you want to apply the discount to. For example, to apply it to the third order, enter 2.
- Actions:
- Apply Discount
- Send Communication (Klaviyo or Attentive)
Variations
- Combine with a Klaviyo pre-notification. Send a "your next order will be 20% off" email before the qualifying order places.
- Test discount levels. Run separate Workflows at different discount percentages to find the level that maximizes retention without over-discounting.
- Combine with a gift for higher-value milestones. Use a discount at the second order, then a free gift at a later milestone, like the sixth order.
Template available: This recipe has a one-click template. Click Create Workflow and choose it from the templates, or follow the steps below to build it from scratch and see what each step does.
Objective
Move the place date on a group of upcoming orders at once, without editing each subscription by hand.
When to use this
This recipe is a good fit if:
- A fulfillment or logistics issue means a batch of upcoming orders needs to ship later than scheduled.
- You want to line a group of orders up on a specific date, like the first of the month.
- You'd otherwise send a bulk date change request to Ordergroove Support.
It's not the right fit if you want dates to move on an ongoing basis. That's a recurring Workflow rather than a one-time run; see Variations below.
Customer experience
- The customer's subscription and upcoming order are scheduled as normal.
- You run the Workflow against the orders you've selected.
- The place date on those orders moves to the date you chose.
- The customer sees the new date for their next order in the Subscription Manager.
Setup
- Trigger: Manual Execution (the Workflow runs once, when you click Execute)
- Data: raw input or CSV upload, with
orderas your column header. See Providing data for manual recipes. - Actions:
- Change Order Place Date, set to the new date you want
- Click Execute to run the Workflow against your records. We recommend running it on a single record first; see Testing a Workflow.
Variations
- Move order dates automatically. If you want dates to move on an ongoing basis rather than once, swap Manual Execution for a recurring trigger. For example, trigger on Subscription Created and set the place date to the first of the next month, so every new subscription lands on the same billing cycle.
Template available: This recipe has a one-click template. Click Create Workflow and choose it from the templates, or follow the steps below to build it from scratch and see what each step does.
Objective
Cancel a defined set of subscriptions in a single pass.
When to use this
This recipe is a good fit if:
- You're discontinuing a subset of subscriptions and need them all closed at the same time.
- You need to cancel for regulatory or compliance reasons, such as a product you can no longer ship to certain customers.
- You'd otherwise send a bulk cancellation request to Ordergroove Support.
It's not the right fit if you're discontinuing a single product across the board; use the Discontinue Wizard for that (see Discontinuing Products on Ordergroove). It's also not the right fit if you need to cancel quietly, since cancellations made this way notify customers.
Customer experience
- The customer's subscription is active as normal.
- You run the Workflow against the subscriptions you've selected.
- Those subscriptions are canceled, and Ordergroove sends its standard cancellation events.
- Any cancellation communications you've set up are sent, exactly as they would be if the customer had canceled on their own.
⚠️ Customers Are Notified
Canceling this way isn't silent. It sends the same cancellation events and customer communications as a normal cancellation, and silent cancellation isn't supported. If your program sends a cancellation email, plan for your customers to receive it.
Setup
- Trigger: Manual Execution (the Workflow runs once, when you click Execute)
- Data: raw input or CSV upload, with
subscriptionas your column header. Because the action works on a subscription, order records won't link here. See Providing data for manual recipes. - Actions:
- Cancel Subscription
- Click Execute to run the Workflow against your records. Test it first on a single subscription you own; see Testing a Workflow.
Objective
Cancel a subscription automatically once it has received a set number of orders, so a fixed-term commitment ends on its own.
When to use this
This recipe is a good fit if:
- You sell subscriptions with an upfront commitment, like a three-order or six-order term, that should end once the term is complete.
- You sell gift subscriptions purchased on someone else's behalf, where the subscription should stop rather than renew against the gifter's payment method.
- You're tracking terms manually today and canceling those subscriptions by hand.
It's not the right fit if term length varies from customer to customer. The filter matches a single order count, so you'd need a separate Workflow for each term you offer.
Customer experience
- The customer signs up and receives their orders as normal through the term.
- When the final order in the term places, the subscription is canceled.
- Ordergroove sends its standard cancellation events, and any cancellation communications you've set up are sent.
- The subscription no longer appears as active in the customer's Subscription Manager, and no further orders are scheduled.
Setup
- Trigger: Recurring Order Placed
- Filter: Successful Order Count equals the number of the order before the one that should end the term. For example, if the term is 3 orders, enter 2. Toggle the node to the subscription level so it counts the successful orders on that subscription.
- Actions:
- Cancel Subscription
⚠️ Customers Are Notified
Like any cancellation, this sends the standard cancellation events and any cancellation communications you've set up. If the term is a planned ending rather than churn, consider tailoring that message so it reads as the end of a term.
Variations
- End gift subscriptions automatically. Filter to your gift products so a gifted subscription closes after its final order instead of renewing against the purchaser's payment method.
- Run a different Workflow per term. If you offer more than one term length, build one Workflow per term and filter each to the products sold on that term.
Next steps
- Creating Workflows — build a Workflow from a template or from scratch, and connect your email provider.
- Managing Workflows — test, launch, run manually and monitor your Workflows.
- Workflows Reference — every trigger, logic step and action, plus answers to common questions.