Shopify Flow integration

recurrabee emits Shopify Flow triggers on every state transition. This lets merchants automate downstream actions — tagging customers, firing Klaviyo flows, alerting in Slack, adjusting fulfillment — without writing code.

Available triggers

• Subscription activated — contract enters active state
• Subscription paused
• Subscription resumed
• Subscription skipped
• Subscription past-due — billing attempt failed
• Subscription recovered — past-due → active after successful retry
• Subscription cancelled — with reason code in the payload
• Subscription swapped — product/variant changed

Each trigger carries the contract, the customer, and relevant metadata.

Setting up a Flow workflow

1. Shopify Admin → Apps → Flow → Create workflow.
2. Start trigger: pick one of the recurrabee triggers from the list.
3. Add conditions and actions as you would for any Flow workflow.

Example workflows

Tag customers in dunning

• Trigger: Subscription past-due
• Action: Add customer tag in-dunning
• Paired workflow: Trigger Subscription recovered → Remove tag in-dunning

Useful for segmenting in Klaviyo or for suppressing promotional emails to customers who are already in a payment issue.

Slack alert on cancellations

• Trigger: Subscription cancelled
• Condition: cancellation reason = “too expensive”
• Action: Send Slack message to #retention with customer details

Lets the retention team reach out manually to high-LTV cancellations.

Klaviyo flow: post-cancel save

• Trigger: Subscription cancelled
• Action: Send custom event to Klaviyo (Subscription Cancelled)
• Klaviyo: triggers a 7-day re-engagement flow

Flow vs. webhooks

Flow is the right choice when the downstream action is a Shopify-native thing (tags, fulfillment, email via Klaviyo flows). Webhooks are the right choice when you need to hit a custom internal system with structured data. Many merchants use both.