Automations

An automation is one sentence:

When someone does X, if all of these are true, do these things.

Rules run independently per trigger. Up to 50 rules per server.

Rule basics

Rule name

1–60 characters · required

Internal label. Name it after what it does — Welcome role, No links for new members — because in six months the list is the only documentation you have.

Rule enabled

Default true

Turn a single rule off without deleting it. Useful for seasonal rules and for isolating which rule is causing something.

Cooldown

0–86400 seconds · default 0

Per-user re-trigger cooldown. 0 means no cooldown.

Triggers

The event that starts the rule. Exactly one per rule.

A member…

• Sends a message
• Edits a message
• Deletes a message
• Clicks an automation button
• Adds a reaction
• Receives a role
• Loses a role
• Joins a voice channel
• Leaves a voice channel
• Creates a thread
• Joins the server

Trigger filters

Optional narrowing applied before conditions are evaluated — cheaper and clearer than expressing the same thing as a condition.

Channel filters accept category ids too — one category id covers every channel inside it.

Conditions

All conditions must pass (logical AND). Leave the list empty to always run. Up to 20 conditions.

Limits: up to 100 channels, 50 roles, 100 user ids, 100 phrases (1–200 characters each) per condition.

Actions

Executed in order. A failing action is skipped and the rest still run. Between 1 and 15 actions per rule.

Roles

Moderation

Messages

Message content supports the usual placeholders.

Buttons

A send a message action can attach up to five buttons:

The button id is what a button-click trigger matches on. That is the loop that makes automations interactive: rule A posts a message with a button called apply, rule B triggers on a button click filtered to apply and gives out a role.

Economy & XP

These write into the Economy and Leveling plugins — those must be enabled for the action to have anywhere to write.

Worked examples

Auto-role on join

When:  Joins the server
If:    (nothing)
Do:    Give these roles to the user → @Member

Suggestion threads

When:  Sends a message
       Only in these channels → #suggestions
If:    (nothing)
Do:    React to the message with these emojis → 👍 👎
       Create a thread from the message → "Discussion"

No links until level 5

When:  Sends a message
If:    The user has none of these roles → @Level 5
       The message contains one of these words or phrases → http:// https://
Do:    Delete the message
       Send the user a DM → "Links are unlocked at level 5."

A self-service application button

Rule 1
When:  Joins the server
Do:    Send a message → #welcome, "Want to apply?" + button id "apply"

Rule 2
When:  Clicks a button
       Only these button ids → apply
Do:    Give these roles to the user → @Applicant
       Reply to the message → "You now have @Applicant — check #applications."

Behaviour notes

• Rules are independent. Two rules on the same trigger both run; there is no priority or stop-first.
• A rule that would loop (an action re-triggering its own rule) still runs — use cooldowns and channel filters to prevent it.
• Actions the bot lacks permission for are skipped silently; the rest of the rule continues. Check your permissions if an action never seems to happen.
• Role actions are subject to the role hierarchy: Cloudy cannot grant a role above its own.