Trigger-condition-action rules, run from anywhere in your server

• Status chip: ATM_ENABLED (green), ATM_DISABLED (grey), ATM_DRAFT (yellow), ATM_ERROR (red).
• Trigger summary — a one-line description of what wakes the rule up.
• Run counts: today / 7 days, plus last outcome (succeeded / failed / dry run).
• Quick actions: enable/disable toggle, duplicate, delete, open in builder.

• Step 1 — General: name, description, status (Draft / Enabled).
• Step 2 — Trigger: pick one of the 19 trigger types and configure its specific options.
• Step 3 — Conditions: optional gates that filter which events actually fire the rule.
• Step 4 — Actions: ordered list of what the rule does. Up to maxActionsPerRun.
• Step 5 — Options: trigger mode, failure policy, cooldowns, dry-run override.
• Step 6 — Review: diff against the published version, dry-run preview, publish or save as draft.

• MESSAGE_CREATED — fires on every new message. Filter aggressively with conditions.
• MESSAGE_EDITED — fires when a message is edited.
• MESSAGE_DELETED — fires when a message is deleted (most actions cannot reference the deleted content).
• REACTION_ADDED — fires when any reaction is added; condition emoji is narrows it.

• MEMBER_JOINED — new member arrives. Most-used trigger for verification flows.
• MEMBER_LEFT — member leaves or is kicked.
• ROLE_ADDED — a role is added to a member. Useful for promotion announcements.
• ROLE_REMOVED — a role is removed.
• VOICE_JOINED / VOICE_LEFT — voice channel transitions.

• CHANNEL_CREATED / CHANNEL_DELETED — admin lifecycle events.
• TICKET_CREATED / TICKET_CLOSED — only fire if Tickets module is enabled.
• EVENT_RSVP — fires when a member RSVPs to an Events module event.

• SCHEDULED_CRON — runs on a cron expression in your guild timezone.
• SCHEDULED_INTERVAL — runs every N minutes.
• SCHEDULED_ONCE — runs once at a specific date and time, then disables itself.
• MANUAL_RUN — only fires when you click Run Now from the Library card. Great for testing.

• contentMatches — substring or regex match against the message.
• messageCountInWindow — author has posted N messages in the last X minutes (rate-limit guards).
• accountAgeMs — Discord account is younger / older than threshold (anti-raid).
• joinRatePerMinute — server-wide join rate exceeds N (anti-raid).
• hasRole — author has (or does not have) a role.
• channelIs — event happened in (or not in) a specific channel or category.

• SEND_MESSAGE — post in a channel. Supports template variables.
• SEND_DM — DM the triggering user. Falls back to a public ping if DMs are closed.
• ADD_REACTION — add an emoji to the source message.
• DELETE_MESSAGE — delete the source message.
• ADD_ROLE / REMOVE_ROLE — modify the triggering user's roles.
• High-risk (off by default): TIMEOUT_USER, KICK_USER, BAN_USER.

• Diff vs. the currently published version (if any) — added/removed steps shown side by side.
• A dry-run preview against synthetic events you can edit in-place.
• Validation errors — missing required fields are blockers; warnings (e.g., no conditions on MESSAGE_CREATED) are non-blocking.
• Two buttons: Save Draft (green when valid) and Publish (only enabled when zero blockers).

• Anti-raid: new account quarantine — MEMBER_JOINED + accountAgeMs < 7 days → ADD_ROLE (Probation).
• Reaction-role gate — REACTION_ADDED on a specific message → ADD_ROLE.
• Daily standup — SCHEDULED_CRON 09:00 weekdays → SEND_MESSAGE in #standup.
• Goodbye logger — MEMBER_LEFT → SEND_MESSAGE in #server-log.

ATM_SUCCEEDED

All actions ran cleanly. The intended side-effects happened.

ATM_FAILED

At least one action errored under FAIL_FAST, or the rule itself raised. Click to see the stack.

ATM_DRY_RUN_OK

Rule matched and would have run — Safe Mode or rule-level dryRun was on, so nothing happened.

ATM_BUDGET_EXCEEDED

The rule was rate-limited by maxRunsPerMinute or maxActionsPerRun.

ATM_SKIPPED

Trigger fired but a condition rejected the event. Expected most of the time.

• string — names, IDs, channel names.
• number — counters and thresholds.
• boolean — feature flags.
• duration_ms — for cooldowns and time windows.

Start at AutomationsRulesBuilder.

• Step 1 — name the rule "Welcome DM", leave status as Draft.
• Step 2 — pick MEMBER_JOINED.
• Step 3 — leave conditions empty (we want every join).
• Step 4 — add SEND_DM action with a friendly message and the {{user.mention}} placeholder.
• Step 5 — defaults are fine.
• Step 6 — Save Draft, then Run Now from the Library to test on yourself, then Publish when happy.

• Builder Step 2: MEMBER_JOINED.
• Step 3: add condition accountAgeMs with operator < and value 7 days.
• Step 4: ADD_ROLE → Probation (you create this role first; deny it from chat channels).
• Step 4 (second action): SEND_DM explaining the verification process.
• Step 6: Publish. Verify by checking Runs after a real join.

• Open Runs and filter by your rule name.
• If you see ATM_SKIPPED rows — your conditions are too tight. Open the row to see which condition rejected.
• If you see ATM_DRY_RUN_OK — Safe Mode is on or rule dryRun is on.
• If you see ATM_BUDGET_EXCEEDED — bump maxRunsPerMinute or add a per-user cooldown.
• If you see no rows at all — your trigger is wrong. Confirm by manually firing MANUAL_RUN.