Rule format

An automation rule can be written by hand and loaded as a file: “Automations → New rule → Load from file”. Here are all the fields, allowed values and limits. A loaded rule arrives turned off: check it in the editor and turn it on.

File

A JSON file (UTF-8 encoding) like this:

{
  "format": "paperbot-automation",
  "guild_id": "123456789012345678",
  "rule": {
    "name": "Remind the author and close",
    "trigger": { "type": "author_silent", "minutes": 1440 },
    "conditions": [
      { "type": "status", "value": "open" },
      { "type": "paused", "value": false }
    ],
    "actions": [
      { "type": "message", "text": "{user}, is the question still relevant?",
        "buttons": [
          { "key": "stillneed", "label": "Yes, I need help", "style": "primary", "who": "author" }
        ] },
      { "type": "wait", "minutes": 1440 },
      { "type": "close", "reason": "The author didn't reply" }
    ]
  }
}

Where to get IDs

• •Server — the number in the web panel address: /dashboard/ID/….
• •Ticket category — the number in its page address: /dashboard/…/categories/ID.
• •Role and channel — the ID on Lolka. IDs are always written as a number or a string of digits.
• •Custom button — a key you make up yourself: 4–16 characters, lowercase Latin letters and digits (stillneed, helped1).

Triggers (rule.trigger)

The type field is required, the rest per the table. Timer minutes are from 5 to 43200 (30 days).

A regex in message is case-insensitive, with no more than one repeat (*, +, {n,m}) and no more than 8 alternatives (?, a|b); the first 1000 characters of the message are checked.

Conditions (rule.conditions)

Each condition is an object with a type. Where there’s op: gte — “at least”, lte — “at most”. A condition with an empty required field is dropped.

Actions (rule.actions)

Steps run in order, up to 10 in the list and in each branch. Texts are up to 2000 characters, and placeholders work in them. A step with an unknown type is dropped; a step without a required field is a load error with an explanation.

Custom button (in message.buttons)

Nesting

• •if_else can go inside repeat or inside another top-level if_else — no deeper.
• •repeat — only at the rule’s top level; no wait or repeat inside it.

What is checked on load

• •The rule arrives turned off — turn it on in the editor after checking (“Check”, “Dry run on a ticket”).
• •If guild_id doesn’t match the server you load it on, or is missing, another server’s roles and channels are dropped: the “Post in a channel”, “Give a role”, “Take a role” steps and the author_role, claimer_role conditions are removed, message loses its ping roles, add_to_ticket and remove_from_ticket lose their roles (the step stays if it has actor: true).
• •Categories that don't exist on this server are dropped: from conditions, from “Move to category”, from the “Moved to category” trigger (it becomes “any”).
• •Unknown fields are thrown away, numbers are trimmed to the limits. Without a trigger or without a single action the rule won't load — the error says what's missing.
• •Ban, kick, unban, roles and ticket access can be turned on only by the server owner or a Lolka administrator.
• •No more than 25 rules per server.