Automations

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. 1

   When this happens

   One trigger, of 22: a member joining, leaving, boosting, being banned, unbanned or timed out, or changing their nickname; a role gained or lost; a message sent, edited or deleted; a reaction added or removed; voice joins, leaves and moves; a thread, channel or invite created; an automation button clicked; and a schedule.

2. 2

   If these are true

   Up to ten conditions narrow it: where it happened, who it was (roles, named people, bots, account age, time in the server), what the message said or carried, and which reaction, role, voice channel or button it was. Match All of these or Any of these.

3. 3

   Then do this

   Up to ten actions, in order: send, reply, DM, repost or start a thread; delete, pin, publish or react to the message; give, take or toggle roles; time out, kick, ban or rename the member; set a channel's slowmode, lock or unlock it; and wait (up to 15 minutes) between steps.

A server keeps up to five automations. New ones open as drafts: Save draft keeps one without running it, and Publish puts it live.

Templates

Arclo ships six ready-made rules to start from: Give everyone a starter role, Block Discord invites, Media-only channel, Flag brand-new accounts, Auto-thread every post and Scheduled announcement. Each arrives with its trigger, conditions and message written, so what is left is pointing it at the channel or role it needs. There is no welcome template, because Welcome & Goodbye is better at it, and word filters and mass mentions belong to Auto Moderation, which adds escalation and exemptions.

Scheduled rules

Once

A date and a time, in the rule's own time zone. Editing the date, time or time zone re-arms a rule that has already fired, and a moment already in the past fires as soon as the rule is published.

Interval

Every N minutes (five at the least), hours, days or months, counted from the last run. Months are calendar arithmetic, so 31 January + 1 month is 28 February rather than a fixed number of days.

Run window

An optional start (a date and a time) and end date. The end date is inclusive, so a seasonal rule stops on its own after its last day.

Rotating messages

Up to five designs in one message action, played in order or at random, so a recurring announcement is not the same sentence forever.

Actions that undo themselves

Temporary roles (up to 28 days), temporary bans (up to a year) and automatic unlocks (up to a week) 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. Ignore bots, on by default, keeps other bots out too.
• Chain depth is capped. Role gained → take it away plus role lost → give it back stops after three hops instead of ping-ponging at the rate limit.
• Cooldowns and exemptions are per rule: a wait between runs (Per member, Per channel or Server-wide), and roles and channels it never runs for. A cooldown longer than two minutes is remembered across restarts.
• Active / Paused is the switch on the rule's card in the list, separate from saving. Publishing an edit to a paused rule leaves it paused.

Buttons as a hand-off

A message an automation sends can carry up to five buttons, and another rule can trigger on Clicks an automation button, narrowed to the buttons you pick. 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: a line each time an automation runs, and a separate one when some of its actions failed. Set it at the foot of the Automations page or from Logging.