Automated actions

Automated actions choose an escalation based on earlier protection records for the member.

Configure an action

Sign in, select a server, and open Protection. You must own the server or have Manage Server permission; some filters require Premium. April needs Kick Members and Ban Members even to process protection, plus permissions and hierarchy appropriate to the chosen action. Deletion needs Manage Messages; a timeout needs Moderate Members. Enable the relevant filter, review its exclusions and configure its sanctions first.

1. Open its automated actions and enable filter-specific actions, or use the default actions when filter-specific actions are disabled.
2. Add a threshold and choose a time window with the duration picker. Set a duration where applicable. The API stores both values in seconds; a new action starts with threshold 3, a 30-minute window and a one-hour duration. Saved values may differ.
3. Save and inspect the protection log after an authorized, harmless test. Actions are considered in configured order, at most five; the first whose threshold is met stops the search.

For example, threshold 2 and window 3600 seconds requires two previous, non-deleted protection logs for that member in the preceding hour. The current match is recorded afterward, so it may act on the third match. These records are counted across filters, not only this filter. A deleted record does not count.

The new Mute action is unsaved; this form does not show its stored duration control.

Action limitations

Delete and Warn are immediate filter sanctions; Warn invokes the configured notification, not an independent punishment. Current Worker behavior differs from some action labels:

• Mute applies a Discord communication timeout using the stored duration. The form shows the duration control for Timeout and Temp ban, not Mute; a new action starts with a one-hour stored duration. It is not added to the recorded punishment list.
• Kick removes the member; Ban creates a ban. The source passes zero delete-history seconds (the seconds component of seven days), not a seven-day ban duration.
• Soft ban creates a ban and does not perform an unban. Timeout (TempMute) does nothing in this handler. Temp ban, Unmute and Unban are displayable identifiers but are not offered by the action selector; TempBan is a no-op and Unmute and Unban have no handler cases. A qualifying no-op still stops later actions.

Do not rely on these labels as a complete moderation workflow. Check actual Discord state and permissions after a test. If the outcome is unexpected, disable the action, review prior protection records and correct any Discord state manually. A saved setting or log alone does not prove a Discord action succeeded.