How to Create an Automation Rule in IZI
How to Create an Automation Rule in IZI
Section titled “How to Create an Automation Rule in IZI”An automation rule is an instruction: “when event X occurs, if condition Y is met, perform action Z”. Set it up once, and it runs without any admin involvement. Here is the full creation process.
Step 1 — Open the Automation section
Section titled “Step 1 — Open the Automation section”In the sidebar, select your organization → Automation → click Create rule. The configuration form will open.
Step 2 — Fill in the general settings
Section titled “Step 2 — Fill in the general settings”| Field | What to enter |
|---|---|
| Rule name | A short label. Example: “10% bonus on top-up from 500” |
| Description | Optional. Notes for the team — why the rule was created, expiry date |
| Rule active | On/off toggle. Enable it now if you are ready to go live |
| Clubs | Leave empty = all clubs. Select specific ones = only those |
Step 3 — Choose a trigger event
Section titled “Step 3 — Choose a trigger event”The event is what must happen for the rule to fire. One rule — one event. Choose from the list:
| Event | When it fires |
|---|---|
| Session completed | Client ends a gaming session |
| Balance top-up | Client tops up their gaming balance |
| Order payment | Client pays for an order at the bar or shop |
| Balance withdrawal | Funds are deducted from the client’s balance |
| Group assigned | Client is added to a group |
| Group unassigned | Client is removed from a group |
Full description of each event → Triggers catalog.
Step 4 — Add conditions (optional)
Section titled “Step 4 — Add conditions (optional)”Conditions filter which clients the rule fires for. Without conditions, the rule runs for all clients who triggered the event.
Click Add condition. For each condition, choose:
- What to check — a client parameter (hours played, amount spent, group membership, etc.)
- Operator — ≥, >, ≤, <, =, ≠
- Value — a number or group
Multiple conditions are joined with AND (all must be met) or OR (at least one). Conditions can be nested in groups for complex logic.
Full parameter list and examples → Rule conditions.
Step 5 — Add actions
Section titled “Step 5 — Add actions”An action is what happens when the rule fires. Click Add action and choose a type:
Accrue bonuses — credited to the client’s bonus account. Enter a formula for the amount. You can use event variables:
- On balance top-up:
{{topup_amount}} * 0.1— 10% of the top-up amount - On session completed:
{{session_duration}} / 3600 * 5— 5 bonuses per hour - Fixed amount:
100
Send notification — to the IZI mobile app. Enter a title (up to 40 characters) and message (up to 120 characters). Event variables can be used in the text.
Assign group — add the client to the selected group.
Unassign group — remove the client from the selected group.
Add multiple actions — they execute sequentially. For example: accrue bonus → send notification about the accrual.
Full description of each action → Actions catalog.
Step 6 — Save and verify
Section titled “Step 6 — Save and verify”Click Save. The rule will appear in the automation list.
To confirm the rule is working:
- Run a test operation — for example, top up a test client’s balance
- Open the rule → History tab
- Check the status of the last entry: Completed — all good, Skipped — conditions were not met, Error — problem with an action
More on troubleshooting → Execution history.
Example: 10% bonus on top-up from 300
Section titled “Example: 10% bonus on top-up from 300”A quick example to get started:
- Name: 10% bonus on top-up from 300
- Trigger: Balance top-up
- Condition: Top-up amount ≥ 300
- Action 1: Accrue bonuses — formula
{{topup_amount}} * 0.1 - Action 2: Send notification — “You received a 10% bonus on your top-up!”
More on building a progressive deposit bonus ladder → Deposit bonus.
See also
Section titled “See also”Frequently asked questions
Does the rule take effect immediately after saving?
Yes, if the Rule active toggle is on when you save. The first execution will happen on the next matching event for any client.
Can I edit a rule after it has already fired several times?
Yes. Edits apply to future executions — past history is not changed. For a clean measurement of changes, it is better to create a new rule and disable the old one.
How do I test a rule before going live?
Enable the rule and perform a test operation manually (for example, top up a test client's balance). Then open the rule's history and check the status of the last execution.
Can I add multiple actions to one rule?
Yes. Click Add action as many times as needed — they execute sequentially. For example: accrue bonus → send notification.
What does the Clubs field do when creating a rule?
If left empty, the rule applies to all clubs in the organization. If you select specific clubs, it only runs in those. Useful for local promotions.