Automations wait for something to happen in your server, check your conditions, and carry out actions in order. Any action can wait first, from a few minutes to 30 days. The module is off by default; switch it on per server in the dashboard.
- A builder that reads as a sentence: When, Only if, Then
- Triggers: member joins or leaves, gets or loses a role, sends a message (optionally in chosen channels), opens a ticket
- Conditions: has or lacks a role, account age, message text
- Actions: give or take a role, post in a channel, DM the member, notify staff, add a note, each with an optional delay
- Role and channel pickers, and a plain-language summary of every automation
- Templates and JSON import/export; imported automations stay off until you switch them on
Enable the module
Open Automations in your server dashboard and enable the module.
Choose WHEN
Pick the event that starts it, for example a member joining or getting a role. For a role you also pick which role.
Add IF conditions
Optionally require a role, a missing role, an account age or text in the message.
Define THEN actions
Give or take a role, post in a channel, DM the member, notify staff or add a note. Messages can use {user}, {username}, {server}, {role} and {channel}.
Optional delays
Give any action a delay in minutes, hours or days. Delayed actions are scheduled and still run after a bot restart.
In plain words
Under the builder, the automation is spelled out as one sentence, so you can check what it will do before saving.
Loops are capped
One automation runs at most five times a minute for the same member, so two automations that undo each other cannot keep going.
The bot reads enabled automations every ten seconds, so a change takes effect almost right away. Bots never set off an automation.
Module gate
Nothing runs while the Automations module is switched off for the server.