Automations
If this, then that - without writing code.
What it does
Many admin tasks are mechanical: grant a role after a reaction, alert the team when a suspicious member joins, post a reminder every week.
The Automations module chains them as rules: a trigger, optional conditions, one or more actions.
It is the brick that ties the other modules together.
What you can do
- Triggers: arrival, departure, role gained or lost, message, reaction, voice, boost
- Conditions: a role held, a channel, the age of the account, a range of hours
- Actions: message, role, reaction, pin, thread, sanction
- Several actions in a row, with a wait between them
- A test that shows what a rule would do, without doing any of it
How to set it up
4 steps · about 3 minutes
-
1
Choose the trigger
This is the event that starts the rule. Begin with a simple case, such as a member joining.
-
2
Add conditions
Optional. They narrow the rule: only in this channel, only for that role.
-
3
Describe the actions
They run in order. A delay can be inserted between two actions.
-
4
Test before enabling
Test mode shows what the rule would do, without actually running anything.
Limits
Free
10
automations
Premium
100
automations
Frequently asked questions
Can a rule trigger another one?
It can, and the chains are bounded — three deep — so a pair of rules feeding each other stops instead of filling your server. A rule posting into the very channel its trigger watches is refused outright.
Why is there no "level reached" trigger?
Because levels are counted inside another module, and reading its events would mean wiring this one into all the others. It is a real gap and it is written down rather than half-built.
Related modules
Ready to try it?
This module is free. Invite the bot and enable it in two clicks.
Add to Discord