Creating Your First Automation Rule in IZI: Step-by-Step Guide
Creating Your First Automation Rule in IZI
Section titled “Creating Your First Automation Rule in IZI”The best way to understand automations is to create one simple working rule. In this guide we build a welcome mechanic: client finishes their first session → receives a bonus and a notification. The scenario is concrete and useful — use it as a template for any other rules.
If you want to understand the overall automation logic first → Automation in IZI: Overview.
What We’re Building
Section titled “What We’re Building”Rule: “Welcome Bonus for First Session”
- Event: client finished a gaming session
- Condition: this is their first session (session count = 1)
- Action 1: award 50 bonuses to account
- Action 2: send “Welcome!” notification
Adjust the bonus amount to your average rate. Guideline: 50–100 bonuses with an average rate of 200–500 — that’s ~15–25% of a session, enough for the client to return and spend it.
Step 1 — Open the Automation Section
Section titled “Step 1 — Open the Automation Section”In the sidebar, select the organization → Automation → click Create Rule. A configuration form opens.
Step 2 — Fill In General Settings
Section titled “Step 2 — Fill In General Settings”| Field | What to Enter |
|---|---|
| Name | ”Welcome bonus — first session” |
| Description | Optional. You can write “Award 50 bonuses to new clients on first session” — useful if other administrators will edit the rules |
| Rule active | Enable — the rule starts working immediately after saving |
| Clubs | Leave empty (all clubs) or select one club for testing |
Tip: on first launch, select one club. Confirm everything works — then expand to the network.
Step 3 — Select the Trigger Event
Section titled “Step 3 — Select the Trigger Event”Click the Trigger Event field and select Session ended.
This event fires when an administrator closes a client’s session or it ends when the rate expires. After selecting the event, the form shows variables available in this rule’s conditions and actions.
Full event list → Trigger Event Catalog.
Step 4 — Add “First Session” Condition
Section titled “Step 4 — Add “First Session” Condition”Click Add condition. Configure:
- Parameter: Session count (visit_count)
- Operator:
= - Value:
1
This means: the rule fires only when the client’s first session has just ended. On the second, third, and subsequent sessions — the rule checks the condition, sees visit_count > 1, and skips.
Step 5 — Add “Award Bonuses” Action
Section titled “Step 5 — Add “Award Bonuses” Action”Click Add action → select Award bonuses.
| Parameter | Value |
|---|---|
| Amount formula | 50 — fixed 50 bonuses |
| Bonus expiry | 30 days — creates an incentive to return before expiry |
The formula can be any number or expression. For a fixed welcome bonus, writing the number directly is simplest: 50, 100, 200.
If you want to award a percentage of the first session’s duration — use {{session_duration}} / 3600 * N where N = bonuses per hour. But for a welcome scenario, a fixed amount is clearer.
Step 6 — Add “Send Notification” Action
Section titled “Step 6 — Add “Send Notification” Action”Click Add action again → select Send notification.
| Field | Value |
|---|---|
| Title | ”Welcome!” (up to 40 characters) |
| Message | ”Great to have you! Welcome bonuses are in your account — try them on your next session.” (up to 120 characters) |
Place the notification after bonus award — that way when the client opens the app, the bonus is already in their account.
The notification arrives through the IZI mobile app. Clients without the app won’t receive it — this is normal, not an error.
Step 7 — Save the Rule
Section titled “Step 7 — Save the Rule”Click Save. The rule appears in the automation list.
Final configuration:
| Element | Setting |
|---|---|
| Name | Welcome bonus — first session |
| Event | Session ended |
| Condition | Session count = 1 |
| Action 1 | Award 50 bonuses, 30-day expiry |
| Action 2 | Notification “Welcome!” |
| Status | Active |
Step 8 — Verify the Rule Works
Section titled “Step 8 — Verify the Rule Works”Testing is done on a test client — not a real one.
- Register a test client (can use your own phone number)
- Open and close a session for them
- Navigate: Automation → “Welcome bonus — first session” → History tab
- An entry with status Completed should appear
- Open the test client card → check bonus balance: should be 50 bonuses
If status is Skipped — the condition wasn’t met. Check the test account’s visit_count: the test account may have had previous sessions, making visit_count greater than 1.
If status is Error — open the entry and read the details. Most common cause is an incorrect formula or action configuration error.
What’s Next
Section titled “What’s Next”The rule is working. Now you can:
- Duplicate the template — for bonuses on the 2nd, 5th, 10th session (change the condition to the target
visit_count) - Add a progressive top-up bonus ladder → Top-Up Bonuses
- Build a rank system → Rank System Setup
- Set up dormant client return → Anti-Churn Automation
Typical First-Rule Mistakes
Section titled “Typical First-Rule Mistakes”| Problem | Cause | Solution |
|---|---|---|
| Rule doesn’t fire | ”Rule active” toggle is off | Enable the toggle |
| All clients receive the bonus, not just new ones | Condition not added or added incorrectly | Check condition: parameter = visit_count, operator = =, value = 1 |
| Notification doesn’t arrive | Client doesn’t have IZI mobile app | Normal; check that history status is “Completed” — means IZI sent it |
| No entries in history | Event hasn’t occurred yet | Run a test operation |
See Also
Section titled “See Also”Frequently asked questions
Does the rule start working immediately after saving?
Yes, if the 'Rule active' toggle is enabled. The first firing will occur on the next matching event from any client.
Can a rule be changed after it has already fired?
Yes. Editing only applies to future firings — past history is not changed. For a clean before/after comparison, it's better to create a new rule and disable the old one.
How do I verify the rule is working?
Perform a test operation manually (e.g., open and close a session for a test client). Then open the rule → History tab → check the status of the last entry.
Are conditions required?
No. Without conditions, the rule fires for all clients who experienced the target event. Conditions are needed when you want to restrict the rule — for example, only for the first session or only for top-ups above a certain amount.
Can multiple actions be set in one rule?
Yes. Click 'Add action' as many times as needed — all will execute sequentially. Typical order: award bonus first, then send notification.