Triggers Catalog for IZI Automation
Triggers Catalog for IZI Automation
Section titled “Triggers Catalog for IZI Automation”A trigger event is what causes a rule to check its conditions and execute its actions. One rule — one event. If you need one mechanic for multiple events, create several rules.
How to create a rule with the right event → Create an automation rule.
Session completed
Section titled “Session completed”Fires when a client ends a gaming session — either the admin closes the session or it closes automatically when the tariff expires.
Available variables:
| Variable | What it contains |
|---|---|
{{session_duration}} | Session duration in seconds |
{{total_hours}} | Client’s total play time across all sessions, in hours |
{{visit_count}} | Client’s total number of completed sessions |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Accrue a bonus per hour of play:
{{session_duration}} / 3600 * 10 - Move clients into rank groups based on accumulated hours
- Send a notification after every 10th session (condition:
visit_countdivisible by 10)
Balance top-up
Section titled “Balance top-up”Fires when funds are added to the client’s account — by an admin in cash, by card, or through the IZI mobile app.
Available variables:
| Variable | What it contains |
|---|---|
{{topup_amount}} | Top-up amount |
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Client’s total session count |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Progressive deposit bonus: percentage of
{{topup_amount}}when a threshold condition is met - Notify the client about accrual: “You received X bonuses”
- First top-up: condition
visit_count = 0— welcome bonus for new clients
Order payment
Section titled “Order payment”Fires when a client pays for an order at the club’s bar or shop.
Available variables:
| Variable | What it contains |
|---|---|
{{order_total}} | Full order amount |
{{paid_with_bonuses}} | Portion of the amount paid with bonuses |
{{paid_with_real}} | Portion of the amount paid with real balance |
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Client’s total session count |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Bar cashback:
{{order_total}} * 0.05— 5% to bonus account - Cashback only on the real-balance portion (no double-counting bonuses):
{{paid_with_real}} * 0.05 - Notification about cashback accrual
Balance withdrawal
Section titled “Balance withdrawal”Fires when funds are deducted from the client’s balance — when paying for a session, an order, or a manual deduction.
Available variables:
| Variable | What it contains |
|---|---|
{{withdrawal_amount}} | Amount withdrawn |
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Client’s total session count |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Notify the client of every deduction for balance awareness
- Accrue a bonus on large single withdrawals (incentive to spend more at once)
Group assigned
Section titled “Group assigned”Fires when a client is added to a group — manually by an admin or by another automation rule.
Available variables:
| Variable | What it contains |
|---|---|
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Client’s total session count |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Notify the client of a new rank or status: “You reached Gold rank!”
- Accrue a welcome bonus when joining a VIP group
- Trigger a chain: another rule adds to a group → this rule sends a notification
Group unassigned
Section titled “Group unassigned”Fires when a client is removed from a group — manually or via an automation rule.
Available variables:
| Variable | What it contains |
|---|---|
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Client’s total session count |
{{total_spent}} | Client’s total amount spent |
Typical use cases:
- Notify the client about a status change when transitioning between ranks
- In the rank system — removing one rank triggers a notification about moving to the next
Variables available in all events
Section titled “Variables available in all events”These variables work in any rule regardless of the event:
| Variable | What it contains |
|---|---|
{{total_hours}} | Client’s total play time in hours |
{{visit_count}} | Total session count |
{{total_spent}} | Total amount spent |
See also
Section titled “See also”Frequently asked questions
Can one rule have multiple trigger events?
No, one rule — one event. If you need the same action for different events, create two separate rules with identical actions.
Does the 'Group assigned' event fire on manual assignment or only through automation?
Both — when an admin adds the client manually, and when another automation rule adds them. Watch for chain reactions: rule A adds to a group → rule B fires on 'Group assigned'.
How do I see how many times a specific event fired over a period?
In the rule's execution history — each entry has a date and time. For aggregated event statistics, check the Analytics section.
Is {{topup_amount}} the amount before or after the bonus is added?
It is the top-up amount itself (what the client deposited). The bonus is accrued on top of it and is not deducted from topup_amount.