Trigger actions
A trigger runs its actions in order, top to bottom. A trigger can have up to 10 actions.
Every action can have its own conditions (up to 20) as a per-action guard: if the action’s conditions don’t pass, that action is skipped and the trigger moves on to the next one. Per-action conditions use the same rules as the trigger’s own conditions — see Trigger conditions.
Template variables ({player.name}, {message}, etc.) work in text fields — see the templates guide.
If an action fails (a bad webhook URL, an RCON error, and so on), that failure is recorded and the trigger keeps running the rest of its actions — one broken action doesn’t stop the others.
Sends an RCON command to the server.
| Field | Limit | Description |
|---|---|---|
| Command | 2000 characters | The RCON command to send. Template variables are substituted before sending. |
| Conditions | 20 | Per-action guard (optional) |
The command can’t contain a line break — that would inject a second command.
Webhook
Section titled “Webhook”Sends an HTTP request to an external URL.
| Field | Limit | Description |
|---|---|---|
| URL | 2000 characters | Destination URL. Must use https://. |
| Method | — | POST, GET, PUT, PATCH, or DELETE |
| Body | 8000 characters | Request body (typically JSON). Template variables are substituted with JSON-safe escaping. |
| Headers | up to 20 | Custom HTTP headers |
| Conditions | 20 | Per-action guard (optional) |
If the URL is empty or invalid, the action fails and is recorded as failed — it does not silently skip.
The URL is checked again right before the request goes out (blocking private/internal addresses and redirect tricks). The request times out after 8 seconds.
Bans the player who triggered the event.
| Field | Limit | Description |
|---|---|---|
| Reason | 500 characters | Ban reason. Template variables are substituted. Can’t contain a line break. |
| Duration | — | Hours until the ban expires. 0 = permanent. |
| Scope | — | One server (the server the event happened on) or all servers in your organization |
| Conditions | 20 | Per-action guard (optional) |
If you run the trigger manually, the ban is recorded as issued by you. If it’s fired by an event or a schedule, it’s recorded as a system ban with no operator attached. If there’s no player to ban (a server-scoped event with no subject), the action is skipped.
Adds the player who triggered the event to a roster group.
| Field | Limit | Description |
|---|---|---|
| Group | 500 characters | The roster group to add the player to |
| Conditions | 20 | Per-action guard (optional) |
Adding a player who’s already in the group has no effect. If the group doesn’t exist, or the player has no usable identity to assign, the action is skipped.
Adds a note to the player’s profile.
| Field | Limit | Description |
|---|---|---|
| Note text | 8000 characters | Note body. Template variables are substituted. Line breaks are fine. |
| Conditions | 20 | Per-action guard (optional) |
If you run the trigger manually, the note is recorded as authored by you. If it’s fired by an event or a schedule, it’s recorded as a system note.
Pauses the rest of the trigger’s actions for a set number of seconds.
| Field | Limit | Description |
|---|---|---|
| Seconds | 0–300 | How long to pause |
| Conditions | 20 | Per-action guard (optional) |
The pause happens inline while the trigger runs — a delay close to 300 seconds risks timing out. Actions after the delay see the same event data captured at the start; live server state isn’t re-checked.
Group warn
Section titled “Group warn”Sends an in-game warning to every member of the triggering player’s squad at the moment the action runs.
| Field | Limit | Description |
|---|---|---|
| Message | 2000 characters | Warning text. Template variables are substituted. Can’t contain a line break. |
| Conditions | 20 | Per-action guard (optional) |
Needs a player subject and that player to currently be online with a squad. If the player has no squad, or nobody’s online to check against, the action is skipped.
Notify
Section titled “Notify”Writes an entry to the Audit log.
| Field | Limit | Description |
|---|---|---|
| Title | 500 characters | Notification text. Template variables are substituted. Line breaks are fine. |
| Conditions | 20 | Per-action guard (optional) |
Shows up in the Audit log, filterable by the Notify category. If there’s a player subject, the entry links to that player.
Limits summary
Section titled “Limits summary”| Limit | Value |
|---|---|
| Actions per trigger | 10 |
| Conditions per action | 20 |
| Webhook body | 8000 characters |
| RCON command | 2000 characters |
| Ban reason / group / short text fields | 500 characters |
| Delay | 300 seconds |
| Webhook headers | 20 |