Create your first trigger

Triggers let heliana react to game events automatically — warn a player, run an RCON command, post to a Discord webhook — without anyone having to watch the live feed. You configure the event and conditions once; heliana fires the action every time they are met.

Open the Triggers page

Navigate to your server and click Triggers in the sidebar. The page shows a table of all triggers for this server, with columns for Name, Type, and Enabled.

New organizations start with a set of ready-made triggers already in this table, all switched off. You don’t have to build from scratch — turn one on and adjust it, or build your own with New trigger.

Example: Teamkill autoban

A good first trigger for any Squad server is automatic teamkill enforcement. Find Teamkill autoban in the table and click Edit on its row to open the builder.

It’s pre-filled with:

• Name — Teamkill autoban
• Event — teamkill, which fires every time heliana detects a teamkill from the Squad log
• A counter that tracks teamkills per attacker over a one-hour rolling window
• Two actions: warn the attacker on each teamkill below 7 in that window; issue a one-hour server ban once the counter reaches 7

This trigger is only possible because heliana reads the Squad log. Teamkill events are not available through RCON; without log access you cannot build this automation at all.

Review the configuration, switch Enabled on, then click Save. The trigger appears active in the table immediately and begins firing on the next qualifying event.

Adjust the configuration

Click Edit on any trigger row to reopen the builder. From there you can:

• Change the counter threshold (for example, lower it to 5 on a stricter server).
• Add or remove actions (for example, add a Discord webhook notification alongside the ban).
• Toggle Enabled off to disable the trigger without deleting it.

Building your own

Click New trigger to open an empty builder. Pick the kind — Event (fires on a game event), Manual (a button your team clicks on a player or server), or Scheduled (runs on a timer or cron schedule) — then fill in the event or schedule, conditions, and actions yourself.

Other ready-made triggers

Alongside Teamkill autoban, your organization starts with several other triggers, also switched off until you enable them:

• Warn player and Ban player — manual triggers that add a button to the player profile for your team to use directly.
• Playtime command (!time) — fires on a chat event when a player types !time and replies in-game with their total playtime. This is an example of a chat-keyword trigger.
• Discord log — posts chat or other events to a Discord webhook in real time.
• SL kit enforcement — a scheduled trigger that warns squad leaders on a timer if they have not taken the SL kit.

---

For a complete explanation of how event triggers work, see Create an event trigger. For the full list of ready-made triggers and what each one does, see Use trigger templates.

Next: Next steps