Arclo

Automations

If this happens in your server, do that. One trigger, a list of conditions, an ordered list of actions — with a scheduler, deferred undo and a loop guard.

On this page

Automations is the general-purpose rule engine. Everything else in Arclo does one thing well; this does the thing your server needs that nothing else covers.

The shape of a rule

  1. One trigger

    What sets the rule off. Twenty-two of them: joins, leaves, messages, edits, reactions, role changes, voice activity, threads, boosts, bans, invites, button clicks, and a scheduler.

  2. Conditions

    Narrowing. Only in these channels, only for members with this role, only when the message matches, only outside these hours. Match all or any.

  3. Actions, in order

    Send a message, give or take a role, add a reaction, create a thread, moderate, lock a channel, wait, and more.

The pickers only offer what the trigger can support

Delete the message does not appear on member joins, because a join has no message. Change the trigger and anything that no longer makes sense is dropped rather than left behind to fail silently.

arclo.gg/dashboard/automations
Nebula Collective/Automations

Automations

Automate server tasks with triggers and actions.

One trigger, then conditions, then actions.

Enabled

Trigger

A member gets a role

Conditions

The role is @Booster

Match all

Actions

Send a message in #general

Add the role @Supporter

Wait 30 days

Remove @Supporter

A rule reads top to bottom: what happened, whether it counts, what to do.

Templates

Nine ready-made rules to start from. They deliberately never duplicate a system Arclo already has — there is no welcome template, because Welcome & Goodbye is better at it.

Scheduled rules

Once
A date and a time, in the rule's own time zone. Editing the schedule point re-arms a rule that has already fired.
Interval
Every N minutes, hours, days or months. Months are calendar arithmetic, so 31 January + 1 month is 28 February rather than a fixed number of days.
Run window
A start and an end date, both inclusive, so a seasonal rule stops on its own.
Rotating messages
Up to five designs, played in order or at random, so a recurring announcement is not the same sentence forever.

Actions that undo themselves

Temporary roles, temporary bans and automatic unlocks are recorded as scheduled work rather than held in memory, so they survive a restart. An unlock restores a channel's previous permission state rather than clearing it.

Safety

  • Arclo never sets off its own automations. A rule that posts a message cannot trigger a rule that watches for messages.
  • Chain depth is capped. Role gained → take it away plus role lost → give it back stops after a few steps instead of ping-ponging at the rate limit.
  • Cooldowns and exemptions are per rule: a wait between runs, exempt roles, exempt channels, and an ignore-bots switch. Anything longer than a couple of minutes is remembered across restarts.
  • Active / Paused is separate from saving. Saving a paused rule leaves it paused.

Changes take about twenty seconds

The message trigger fires on every message in the server, so Arclo keeps the whole rule set cached rather than querying per message. Edits reach the bot within roughly twenty seconds.

Buttons as a hand-off

An action can send a message with a button on it, and another rule can trigger on that button being clicked. That is how a multi-step flow is built without a scripting language.

Logging

One logger for the whole system rather than one per rule, with per-action switches. Set it on the Automations list page or from Logging.

Still stuck? Ask in the support server — somebody there has almost certainly configured this before.