Conditions decide when a flow runs. Add them in step 4 of a flow, Add additional conditions (optional). Each condition checks something about the payment, the customer or the partner.
How conditions combine
Click New condition to add one. Between conditions, choose AND (all must be true) or OR (any can be true).
Click New group to group conditions, for example (A AND B) OR C.
A flow with no conditions runs on every trigger.
Each condition takes one value. To match several products, partners or codes, add one condition per value in an OR group.
Transaction conditions
These check the payment itself, so they only work in flows with the New payment trigger.
Condition | Checks |
Amount | The amount of this payment. |
Billing type | Whether the payment is a subscription or a one-time payment. |
Interval | Monthly or yearly billing. |
Product ID | A product on the payment, such as |
Product quantity | How many units were bought, such as seats. You also choose the product IDs it applies to. |
Promotion code | The coupon codes used at checkout. Check whether any code was used (is applied or is not applied), or pick specific codes, or any program, group or partner code. |
Customer conditions
Condition | Checks |
Number of transactions | How many payments this customer has made, including this one and refunded ones. Equals 1 means the first payment. |
Total paid | How much the customer has paid in total. |
Identifier | The customer's email or ID from your payment provider. Case-sensitive. |
Created date | When the customer signed up. |
Conversion date | When the customer first paid. Customers who haven't paid yet never match. |
Partner conditions
Condition | Checks |
Number of transactions | How many payments all of the partner's customers have made. |
Number of customers | How many paying customers the partner has referred. Count all time, or only customers who paid within a recent period, such as the last 90 days. |
Number of leads | How many of the partner's referrals are leads right now, meaning they signed up but haven't paid. The count goes down as leads start paying. |
Partner ID | A specific partner, such as |
Total revenue | How much the partner's customers have paid in total, not counting refunds. |
Total earnings | How much the partner has earned in commissions. |
Total earned per customer | How much the partner has earned from this customer, across all flows. Use less than to cap earnings per customer. Under When the cap is reached, choose to pay the full commission or only the amount left under the cap. |
Sign up date | When the partner joined your program. |
Country | The country on the partner's profile. Pick one or more countries with is in. Partners with no country set may not match. |
Link | The partner link the customer came through. |
Operators
Numbers and amounts: equals, greater than, less than. Greater than and less than don't include the value itself, so "at least 10 customers" is greater than 9.
Text and IDs: equals, not equal to, contains, doesn't contain.
Dates: is within, is after or is before a number of days, months or years, or is after, is before or is within a specific date.
For dates, is within 3 months means less than 3 months ago, and is after 3 months means more than 3 months ago.
Good to know
To give one partner or link a different rate, use an override in the existing flow instead of a separate flow with a Partner ID or Link condition. See Custom rates for a partner or a link.
For worked examples, see Tiered rates by customer count and Time-based commission rates.