Discord Automation, Notifications & Approvals

Messages pile up across your Discord servers faster than you can triage them, and the automations people wire up to respond, assign roles, or remove members rarely pause to ask whether this case is the exception.

When Discord runs unsupervised

Automation that acts on every message treats your server like a queue to drain, not a community to read. One mis-fired action posts publicly, removes the wrong member, or assigns a role to someone who shouldn't have it, and you find out from a screenshot.

• New message trigger fires on every channel: a workflow consumes an entitlement or updates a role connection for a user you'd have flagged manually, and there's no undo that isn't also visible.
• Leave Guild runs without review: a member removal action goes out before you've checked whether the account was actually a bad actor or just a confused new signup.
• Update User Application Role Connection applies at scale: a batch role update ships across your guild before you've confirmed the qualifying criteria still apply this week.
• Consume Entitlement fires on ambiguous eligibility: an entitlement gets consumed for a user whose subscription status you'd have wanted to verify first.

What Rills does inside Discord

Rills sits between the incoming DISCORD_NEW_MESSAGE_TRIGGER and any action it would take, whether that's Update User Application Role Connection, Leave Guild, or Consume Entitlement. Every proposed action queues for your review before it runs, so the communication layer doesn't move without you.

The member removal still happens; you just see it first.

When Discord events should and shouldn't act on their own

Not every message event carries the same stakes. Some patterns are routine enough that you'd approve them every time; others touch things you'd always want to read before they go out.

• DISCORD_NEW_MESSAGE_TRIGGER (greeting keywords, known user): routine enough to graduate toward autonomous once you've approved the same pattern a dozen times.
• DISCORD_NEW_MESSAGE_TRIGGER (first message, unknown user, role assignment proposed): always needs a human; the cost of a wrong role update in a communication platform shows up publicly.
• DISCORD_NEW_MESSAGE_TRIGGER (entitlement or guild membership action proposed): always needs a human; consuming an entitlement or removing guild access isn't reversible without a visible correction.

Approving Discord actions from your phone on a case-by-case basis is how the confidence score learns which message patterns you trust and which ones you don't.