Recipe 1 — Tag customers when payment fails
Use case: Build a “payment-failed” customer segment for a Klaviyo win-back flow or for a support follow-up list.1
Trigger
Pick Circuly: Invoice dunning as the trigger.
2
Action
Add the Add customer tags action. Use the customer reference from the trigger. Tag with
payment-failed.3
Optional: notify support
Add a Send internal email action to email your support team with
{{customer.email}} and {{trigger.invoiceNumber}}.Recipe 2 — Win-back when a contract is cancelled
Use case: Trigger a churn-recovery email series the moment someone cancels.1
Trigger
Circuly: Subscription cancelled.
2
Condition
Add a condition:
{{trigger.cancelledBy}} == 'customer' (skip merchant-initiated cancellations).3
Action
Use Add customer tags with tag
churned-subscription, and connect Klaviyo or your ESP to enroll them in a win-back series triggered by that tag.Recipe 3 — Notify warehouse when an asset is returned
Use case: Tell your fulfillment team to inspect and restock a returned rental unit.1
Trigger
Circuly: Asset returned.
2
Action
Send internal email to
warehouse@yourcompany.com with {{trigger.assetId}}, {{customer.firstName}} {{customer.lastName}}, and {{trigger.condition}}.3
Optional: Slack
If you use the Slack connector for Flow, post the same payload to your
#warehouse channel.Recipe 4 — Segment new subscribers by contract type
Use case: Apply different onboarding emails for Rental vs. Subscription customers.1
Trigger
Circuly: Subscription created.
2
Branch on contract type
Add a condition on
{{trigger.contractType}}. One branch handles Rental, the other handles Subscription/Consumable/Digital.3
Action
On each branch, Add customer tags with
new-rental or new-subscription. ESPs (Klaviyo, Mailchimp) can listen for those tags and trigger the right onboarding journey.