What you configure
| Field | What it is |
|---|---|
| Rule ID | The exact ID of the rule to toggle, from its edit page rather than its name |
| Enabled | On or off |
See Finding a rule's ID for Shopify Flow.
Before you build one
If the signal is a date and time you already know, use the rule's own scheduling instead. Schedule a rule covers start and end dates without a workflow to maintain, and a scheduled rule shows its state honestly in the Rules list.
This action is for the cases scheduling cannot express: a stock level, a collection being unpublished, an approval in another system.
Four workflows worth building
Auto-activate a drop-day rule. Build the rule in advance and leave it deactivated, then use Flow's schedule trigger to activate it exactly when the drop goes live, without being at a keyboard for the moment it happens.
Auto-deactivate when a collection is unpublished. If a rule is scoped to a promotional collection, trigger on that collection being unpublished or archived and deactivate the rule at the same time, so it stops enforcing against something that is no longer live.
Relax limits during a sale, restore them after. Two scheduled workflows, one deactivating a minimum-order rule as a sale opens and one reactivating it when the sale closes.
Activate when stock hits zero. Combine with Shopify's inventory trigger to activate a blocking rule when stock reaches zero, then deactivate it again on restock.
Common mistakes
- Using the rule's name. The field takes an ID.
- Expecting a built-in reverse. The action sets the state you gave it, once. The other direction is a second workflow.
- Underestimating how immediate it is. A deactivated rule stops enforcing straight away, exactly as if you had clicked Deactivate. Make sure a workflow that deactivates something is meant to stop enforcement now.
- Losing track of why a rule is off. A rule switched off by a workflow looks identical in the Rules list to one somebody switched off by hand. See Rule statuses.