What's in a Flow

A Flow consists of three key components:
Triggers
Triggers initiate the flow, defining the “when” of your automation. Mantle Flows offers a wide range of pre-defined triggers, as well as the ability to use custom events.
Example: “When a customer installs my app…”
Some examples of available triggers are:
Event Type | Triggers | Availability |
---|---|---|
App events | • Customer installs, uninstalls, or reinstalls app • Customer deactivates or reactivates app • Subscription approaching or updating capped limit • Usage charge exceeds limit • Customer reviews app • Custom field changed • Customer submits an intake form • App identifies customer for the first time • Shopify access token is no longer valid | Ready to use |
Subscription events | • Subscription is activated • Subscription is cancelled • Subscription is upgraded or downgraded • Subscription is re-activated • Subscription is frozen or unfrozen • Subscription is refunded • Trial is expiring in X days • Trial has expired or been extended • One-time charge activated • Transaction is created • Usage charge is created • Bundle discount applied or removed for app | Ready to use |
Stripe events | • Invoice is finalized • Invoice payment failed | Ready to use |
Usage events | You can also trigger flows based on any custom event you track in your app. This allows for unlimited flexibility in responding to user actions specific to your business. | Requires customer identification and usage events setup |
Conditions (optional)
These add specificity to your triggers. They help you narrow down when the flow should run. Example: “…and they have a tag of ‘New customer’…”
Some examples of available conditions are:
Condition Type | Examples | Availability |
---|---|---|
App attributes | • App install date • App install status • Billed usage last 30 days • App uninstall reason • App access token error reason | Ready to use |
Customer attributes | • Customer name • Customer email • Customer abandoned charge • Customer industry • Customer last 30 day revenue • Customer lifetime value • Customer monthly spend • Customer review rating • Customer Shopify plan • Customer billing platform • Customer tags • Test customer | Ready to use |
Customer custom fields | • Custom field values • Test boolean fields | Requires custom fields setup |
Subscription conditions | • Subscription active • Subscription activation date • Subscription billing interval • Subscription billing platform • Subscription cancelled • Subscription cancel date • Subscription flex billing • Subscription frozen • Subscription frozen date • Subscription plan • Eligible for bundle discount • Has bundle discount applied | Ready to use |
Usage & engagement | • Usage metrics (page view, SKUs, orders, video views, etc.) • Transaction fees | Requires usage events setup |
Email engagement | • Email has had any click | Requires Mantle Email setup |
Affiliate conditions | • Referred by • Referred by any affiliate | Ready to use |
Actions
These are the tasks your flow performs. They define what happens when the trigger (and conditions, if any) are met. Examples of available actions include:
Action Type | Description | Requirements |
---|---|---|
Send email | Send an email to the customer | Requires Mantle Email setup |
Add customer tag(s) | Enter tag(s) to add to the customer. Can also be used to apply specific discounts | Ready to use. For discount application, see Discounts documentation |
Remove customer tag(s) | Enter tag(s) to remove from the customer | Ready to use |
Extend trial | Add additional trial days to a customer’s subscription | Ready to use |
Add timeline comment | Automatically add a comment to the customer’s app timeline | Ready to use |
Populate custom field | Populate a customer’s custom field with a value | Requires custom fields setup |
Assign account owner | Assign an account owner to the customer | Ready to use |
Post Slack message | Post a message to a Slack channel | Requires Slack integration setup |
Send HTTP request | Send a request to an external URL | Ready to use |
Send notification email | Send a notification email to your team | Ready to use |
Together, these components create a complete automation: “When [Trigger] happens, if [Condition] is met, then do [Action].”
Next: Creating a flow