Actions Catalog for IZI Automation
Actions Catalog for IZI Automation
Section titled “Actions Catalog for IZI Automation”An action is what happens when a rule fires. One rule can contain multiple actions — they execute in order. If one action fails, subsequent actions do not run.
How to configure actions when creating a rule → Create an automation rule.
Accrue bonuses
Section titled “Accrue bonuses”Adds an amount to the client’s bonus account. Bonuses are spent according to tariff rules — they cannot be withdrawn as cash.
Parameters
Section titled “Parameters”Bonus formula — required. A number or mathematical expression using event variables.
Variables depend on the trigger event:
| Variable | Event | What it contains |
|---|---|---|
{{topup_amount}} | Balance top-up | Top-up amount |
{{session_duration}} | Session completed | Duration in seconds |
{{order_total}} | Order payment | Full order amount |
{{paid_with_real}} | Order payment | Portion paid with real balance |
{{paid_with_bonuses}} | Order payment | Portion paid with bonuses |
{{withdrawal_amount}} | Balance withdrawal | Amount withdrawn |
{{total_hours}} | Any | Client’s total play hours |
{{visit_count}} | Any | Client’s total session count |
{{total_spent}} | Any | Client’s total amount spent |
Formula examples
Section titled “Formula examples”| Goal | Formula |
|---|---|
| Fixed 50 bonuses | 50 |
| 10% of top-up amount | {{topup_amount}} * 0.1 |
| 5% cashback on bar order | {{order_total}} * 0.05 |
| 5% only on the real-balance portion | {{paid_with_real}} * 0.05 |
| 10 bonuses per hour of session | {{session_duration}} / 3600 * 10 |
| 10% of top-up, capped at 500 | min({{topup_amount}} * 0.1, 500) |
| 100 bonuses for every 10 total hours | floor({{total_hours}} / 10) * 100 |
Bonus expiry — optional. Number of days until the bonus expires. If not set, bonuses never expire. We recommend 30–60 days: it creates an incentive to spend quickly and keeps the club’s liability manageable. More on expiry → Deposit bonus.
Send notification
Section titled “Send notification”Sends a push notification to the client’s IZI mobile app. Delivered only to clients with the app installed and an active session.
Parameters
Section titled “Parameters”| Field | Limit | Example |
|---|---|---|
| Title | Up to 40 characters | ”Bonus credited!” |
| Message | Up to 120 characters | ”You received 150 bonuses for your top-up. Balance is available immediately.” |
The same variables available in bonus formulas can be used in the title and message text.
When a notification is not delivered
Section titled “When a notification is not delivered”- Client has not installed the IZI mobile app
- Client has disabled notifications in device settings
- Client is not signed in to the app
In these cases IZI does not return an error — the notification is considered “sent”, but the client will not see it. For reliable delivery, supplement notifications with other channels (on-screen prompt at the next session launch).
Detailed notification setup guide → Notifications via automation.
Assign group
Section titled “Assign group”Adds the client to the selected group. If the client is already in that group, no error occurs and the status does not change.
Parameters
Section titled “Parameters”Group — selected from the organization’s group list.
Use case
Section titled “Use case”This action is the foundation of the rank system: a rule checks accumulated hours or spending, and when the threshold is reached, adds the client to the rank group.
Adding to a group is itself an event (“Group assigned”), which other rules can react to — for example, sending a notification about the new status.
Unassign group
Section titled “Unassign group”Removes the client from the selected group. If the client is not in the group, no error occurs.
Parameters
Section titled “Parameters”Group — selected from the organization’s group list.
Use case
Section titled “Use case”Used alongside Assign group when transitioning between ranks: the rule for the new rank first removes the old rank (Unassign group), then assigns the new one (Assign group). This prevents a client from holding multiple ranks simultaneously.
Full rank system example using this pattern → Client rank system.
Order of multiple actions
Section titled “Order of multiple actions”If a rule has multiple actions, they execute top to bottom. Recommended order:
- Unassign old groups (if using a rank system)
- Assign the new group
- Accrue bonuses
- Send notification
Put the notification last — by the time the client opens the app, the bonus will already be in their account and they will see the correct balance.
See also
Section titled “See also”Frequently asked questions
Can I add multiple actions to one rule?
Yes. Click Add action as many times as needed — all actions execute sequentially. A typical example: first accrue the bonus, then send a notification about it.
If one action fails, do the rest still execute?
No, execution stops at the first action that fails. The execution history will show which action caused the error.
Will a notification be delivered if the client has not installed the IZI mobile app?
No. Notifications are sent through the IZI mobile app only. If the app is not installed or the client is not signed in, the notification is not delivered — but this is not counted as an error.
Can I use min/max functions in the bonus formula?
Yes, min() and max() are supported. For example, min({{topup_amount}} * 0.1, 500) — accrue 10% of the top-up, but no more than 500.