Conditions

Conditions define when the workflow should continue. If conditions are not met, the workflow stops (or takes the fallback / “otherwise” branch, when configured).

What conditions do

Filter: only continue the workflow when criteria are met
Branch: route customers/subscriptions into different paths
Protect: stop paths that would be irrelevant or unsafe

The Condition block uses a sentence-based rule builder. As you build a condition, smart autocomplete provides context-aware field suggestions. Available fields depend on the trigger (for example, UTM fields only appear on customer-initiated triggers).

Practical examples

Route first-time subscribers vs. loyal subscribers (for example by cycle count or age)
Route VIP vs. non‑VIP subscribers (for example by lifetime value or tags)
Route based on the product the customer is subscribed to
Branch portal flows by UTM source (Customer Portal vs. a tagged email link)
Enforce weight limits on the upcoming order before renewal
Route customers by payment method, or by why their last renewal or payment failed

Conditions reference

`customer.*`

Condition	Description
`customer.revenue`	Total revenue from the customer
`customer.order_count`	Total number of orders from the customer
`customer.tags`	Tags associated with the customer
`customer.created_at`	Date when the customer account was created
`customer.last_payment_status`	Status of the most recent billing attempt across all customer subscriptions (`new`, `pending`, `failed`, `completed`)

`subscription.*`

Condition	Description
`subscription.status`	Current status of the subscription (`active`, `paused`, `canceled`, `expired`, `failed`, `merged`)
`subscription.cycle_count`	Number of completed billing cycles
`subscription.tags`	Tags associated with the subscription
`subscription.item_count`	Number of items in the subscription
`subscription.total_value`	Total monetary value of the subscription
`subscription.age_days`	Number of days since the subscription was created
`subscription.items`	Line items in the subscription (array items include `productId`, `variantId`, `tags`)
`subscription.active_discounts`	Active discounts on the subscription (array items include `type`: `percentage` / `fixed` / `free_shipping`, and `value`)
`subscription.payment_method`	Type of payment method on the subscription: `credit-card`, `paypal`, `shop-pay`, `sepa-direct-debit`, `blik`, `blik-recurring`, `mbway`, `bacs`. `blik-recurring` is a BLIK method with an active recurring mandate
`subscription.last_renewal_failed`	Whether the last renewal attempt failed
`subscription.last_renewal_fail_reason`	Why the last renewal attempt failed: `out-of-stock`, `missing-product`, `billing-attempt-failed`, `no-delivery-method`, `invalid-email-domain`, `draft-order-creation-failed`, `missing-delivery-price`
`subscription.last_payment_error_code`	Error code the payment provider returned for the last billing attempt: `PAYMENT_METHOD_DECLINED`, `INSUFFICIENT_FUNDS`, `EXPIRED_PAYMENT_METHOD`, `CARD_NUMBER_INCORRECT`, `INVALID_PAYMENT_METHOD`, `PAYMENT_METHOD_NOT_FOUND`, `FRAUD_SUSPECTED`, `BUYER_CANCELED_PAYMENT_METHOD`

`subscription_item.*`

Available when the trigger provides a subscription item (for example Subscription item removal requested).

Condition	Description
`subscription_item.productId`	Shopify product ID of the item
`subscription_item.variantId`	Shopify variant ID of the item
`subscription_item.title`	Product title of the item
`subscription_item.quantity`	Quantity of the item in the subscription
`subscription_item.tags`	Tags associated with the product

`upcoming_order.*`

These conditions are used with the Next order updated trigger. They check the state of the next upcoming order. They are not tied to a single subscription when multiple delivery dates exist; per-subscription data is available via upcoming_order.subscriptions.

Condition	Description
`upcoming_order.date`	Scheduled date of the upcoming order
`upcoming_order.item_count`	Total number of line items in the order
`upcoming_order.total_quantity`	Sum of quantities across all line items
`upcoming_order.unique_item_count`	Number of distinct products in the order
`upcoming_order.subtotal`	Order subtotal before shipping and discounts
`upcoming_order.delivery_price`	Delivery/shipping price
`upcoming_order.currency_code`	Currency code of the order (for example USD, EUR)
`upcoming_order.cycle_index`	Billing cycle index for this order
`upcoming_order.skipped`	Whether the order was skipped
`upcoming_order.total_weight`	Total weight of all items in grams (unit weight × quantity). Returns null if any item’s weight is missing from the product index
`upcoming_order.items`	Line items (include `productId`, `variantId`, `title`, `quantity`, `price`, `line_weight_grams`, `subscriptionId`)
`upcoming_order.discounts`	Discounts applied to the order (include `type`, `value`)
`upcoming_order.subscriptions`	Subscriptions on this order (include `id`, `cycleCount`, `itemCount`, `totalValue`)
`upcoming_order.payment_method`	Type of payment method the order will be charged to (same values as `subscription.payment_method`)

`created_order.*`

Available on the Subscription order created trigger. These conditions read the order that was just placed, while upcoming_order.* reads an order that has not been placed yet.

Condition	Description
`created_order.currency_code`	Currency code of the order (for example USD, EUR)
`created_order.subtotal`	Order subtotal before shipping and discounts
`created_order.total_price`	Order total, including shipping and discounts
`created_order.delivery_price`	Delivery/shipping price
`created_order.item_count`	Total number of line items in the order
`created_order.total_quantity`	Sum of quantities across all line items
`created_order.unique_item_count`	Number of distinct products in the order
`created_order.items`	Line items (include `productId`, `variantId`, `title`, `variantTitle`, `sku`, `quantity`, `unitPrice`, `totalPrice`)

`subscription_upcoming_weight`

Standalone condition (not an upcoming_order.* path). Total weight in grams of all items in the subscription’s upcoming order. Useful on triggers that do not carry full order data — especially Customer portal opened — for weight-based rules.

`trigger.*`

Available on customer-initiated triggers. Values come from the UTM parameters on the link that started the flow (for example a tagged link in an email or ad). Empty when the customer opened the portal without UTM parameters.

Condition	Description
`trigger.utm.source`	UTM source
`trigger.utm.medium`	UTM medium
`trigger.utm.campaign`	UTM campaign
`trigger.utm.term`	UTM term
`trigger.utm.content`	UTM content

`time.*`

Condition	Description
`time.hour`	Current hour of the day (0–23, UTC)
`time.day_of_week`	Current day of the week (0 = Sunday, 6 = Saturday, UTC)
`time.date`	Current date/time as an ISO string

`shop.*`

Condition	Description
`shop.setting`	A configuration value from shop settings (params: `key?`, `default?`)

`response.*`

Condition	Description
`response.feedback`	Free-text answer from the first Collect Feedback step submitted in the run (no step id required)
`response.step`	Response from a specific workflow step (params: `stepId`, optional `field`: `type` \| `data`, optional `dataPath`)

`usage_limit` (no `.*` path)

Condition	Description
`usage_limit`	Count of usage-entry records for the given bucket and scope (params: `key`, `scope`, optional `window`)

`display_limit` (no `.*` path)

Condition	Description
`display_limit`	Count of display-entry records for the given bucket and scope (params: `key`, `scope`)

Getting started

Subscription experiences

Workflows

Settings

Integrations

Use guide

What conditions do

Practical examples

Conditions reference

`customer.*`

`subscription.*`

`subscription_item.*`

`upcoming_order.*`

`created_order.*`

`subscription_upcoming_weight`

`trigger.*`

`time.*`

`shop.*`

`response.*`

`usage_limit` (no `.*` path)

`display_limit` (no `.*` path)

​What conditions do

​Practical examples

​Conditions reference

​customer.*

​subscription.*

​subscription_item.*

​upcoming_order.*

​created_order.*

​subscription_upcoming_weight

​trigger.*

​time.*

​shop.*

​response.*

​usage_limit (no .* path)

​display_limit (no .* path)

What conditions do

Practical examples

Conditions reference

`customer.*`

`subscription.*`

`subscription_item.*`

`upcoming_order.*`

`created_order.*`

`subscription_upcoming_weight`

`trigger.*`

`time.*`

`shop.*`

`response.*`

`usage_limit` (no `.*` path)

`display_limit` (no `.*` path)