Skip to main content
A workflow in Shopify Flow starts with a trigger, checks conditions, and runs actions. Supercycle adds its own triggers and actions to that list, so a return, a cycle, a membership, or a failed payment can drive the work. The full list of what Supercycle exposes is on Automation overview.

​
Build a workflow

1

Open Shopify Flow

Go to Flow and select Create workflow.
2

Choose a trigger

Search for Supercycle and pick the event that starts the workflow, such as Return created, Cycle updated, Membership canceled, or Payment collection failed.
3

Add conditions and actions

Add conditions to decide when the workflow acts, loops to walk through a list such as the cycles on a return, and actions to do the work.
4

Test and turn it on

Run Flow’s test with sample data, then turn the workflow on.
Name workflows after what they do, for example Pause subscription on return, so they’re easy to find in a long list.

​
Pause a subscription on return

Pause a customer’s subscription as soon as they start a return.

Pausing subscriptions when returns are created.

1

Add the trigger

Select Return created.
2

Add a loop

Add a For each loop over returnOrder.rentals, so each cycle in the return is handled on its own.
3

Add a condition

Add a Condition that checks the cycle for a subscription.
Condition
4

Add the action

In the Then branch, add Update subscription. Set Subscription ID to {{rentals.foreachitem.subscriptionId}} and Status to paused.
5

Turn the workflow on

Save and turn it on. Subscriptions pause as returns are created.

​
Notify the team on a failed payment

Tell your team when a subscription payment has failed several times.
1

Add the trigger

Select Payment collection failed.
2

Add a condition

Check the attempt count so only repeated failures reach the team.
Condition
3

Add the notification

In the Then branch, add Send internal email. Address it to your support team, give it a subject such as Customer payment failed 3 times, and include paymentCollector.lastFailedPayment.errorMessage in the body.
4

Cancel the subscription (optional)

Add Update subscription after the email. Take the Subscription ID from paymentCollector.subscriptionContractId and set Status to cancelled.
5

Turn the workflow on

Save and turn it on.

​
Resolve item conflicts on a cycle

When a cycle’s allocated item is unavailable, for example because it’s still out on another cycle, let Supercycle pick a fresh one.
1

Add the trigger

Select Cycle updated.
2

Add a condition

Check the cycle for an item or variant conflict.
Condition
3

Add the action

In the Then branch, add Re-allocate item with Cycle ID set to {{rental.id}}.
4

Turn the workflow on

Save and turn it on. Cycles with an item conflict are re-allocated as the conflict appears.

​
Update an item’s condition after its first cycle

Downgrade an item’s condition once it has been out and come back, for example from New to Pre-loved.
1

Add the trigger

Select Cycle updated.
2

Add a condition

Check that the cycle was received and that the item has exactly one completed cycle.
Condition
3

Add the action

In the Then branch, add Update item. Set Item ID to {{rental.item.id}} and Condition ID to the ID of the condition you want, such as gid://supercycle/Condition/456. Copy it from your item conditions settings, or from an item that already has that condition.
4

Turn the workflow on

Save and turn it on. Items move to the new condition after their first completed cycle.

​
Workflow FAQs

Yes. A return can cover several cycles, so walk returnOrder.rentals with a For each loop rather than acting on the first one.
No. Check that subscriptionId exists in a condition before any action uses it, or the step fails on cycles without one.
Use Flow’s test feature with sample data and confirm each branch does what you expect before the workflow runs on real orders.
Check the Flow dashboard for run history. It shows successful runs and the steps that errored, so a broken condition or a missing ID shows up early.