Create an automation

Automations connect conditions to actions. Start with a simple notification, inspect its result, then adjust it to your team’s workflow.

You need Manage automations and rights for the trigger’s domain: sanctions, staff, recruitment, tickets or training. Notifications also require announcement-sending rights. Choose a channel accessible to the bot and appropriate for the information.

Choose a trigger

Trigger	What it checks
Sanction threshold	Recent sanctions for the same player when a new sanction is added, using the selected type and period.
Staff inactivity	A saved-active, nonblacklisted member with no recorded activity for the chosen days.
Application awaiting review	A pending application still at the received stage, older than the selected delay.
Urgent unassigned ticket	An urgent open/waiting ticket still without an assignee after the delay from opening.
Trial ending	An unapproved trial ending soon or already overdue for an active member.
Incomplete required training	A course required for the current rank, not finished by an active member after the selected delay.

The training delay starts at the latest of the member’s arrival, course creation or onboarding start. Never-started training can qualify. Completed steps waiting only for manager approval are not considered incomplete by this alert.

Application reminders measure review state, not a written Discord reply. Ticket reminders measure assignment. Notify a channel excludes categories restricted to specific panel roles; Alert in the ticket channel can include them after checking the channel’s private access. Sanction thresholds concern player records, not internal staff warnings; removed and automation-created sanctions are excluded.

Use a template

The eight templates provide editable starting points: three warnings in seven days, fourteen-day inactivity outreach, thirty-day status updates, recording repeat-offence warnings, applications unreviewed after three days, urgent tickets unassigned after two hours, trials ending within three days, and required training incomplete after seven days.

These are defaults, not mandatory deadlines.

Simulate, save and activate

1. Open Automations, choose a template or create a rule.
2. Give it a clear name and configure its trigger, delay, actions and destinations.
3. Review the summary and run the simulation without execution.
4. Inspect affected targets and planned, skipped or blocked actions. A sanction threshold needs a virtual player/type scenario.
5. Save the rule paused.
6. Activate it from the list only after reviewing and confirming the activation preview.

The simulation sends no messages and changes no statuses or sanctions. Repeat it after editing. It uses current data, so an empty result today can still match future cases; activation can also match older existing cases.

Understand effects

Sanction and inactivity rules may notify a channel, send a DM, add a sanction record or mark staff inactive, depending on rights. A rule contains one to five actions.

Application, ticket, trial and training triggers only send notifications. Notify a channel sends a summary and record links. For urgent tickets, Alert in the ticket channel instead sends a reminder inside each eligible ticket and must be the rule’s only action. These alerts do not make the decision for the team.

Record and status effects

An automated sanction creates a StaffNest record; it does not directly ban or mute on Discord. When used with inactivity, adding that sanction also marks the affected staff inactive. Inspect all simulated effects before activation.

A planned action is eligible; a skipped action has no suitable target or needed effect; a blocked action lacks a prerequisite. Successful simulation is not a guarantee of future message delivery: permissions and DM settings can change.

Avoid duplicate reminders

Inactivity is handled once per member per inactivity period. Another recorded activity followed by a new qualifying inactive period can permit another alert. Editing or toggling the same rule does not reset already handled inactivity. On-leave, inactive and former statuses are not targets.

Record alerts are not resent on every check for the same case or cycle. Changing a trial deadline can create a new alert opportunity. Avoid several equivalent rules aimed at the same channel.

Inspect results and pause

Execution history shows targets, reasons and per-action or recipient results: running, successful, skipped, partial, failed or unconfirmed. Unconfirmed means you should check the channel, DM or profile before repeating the action. A trigger count alone does not prove every message was received. Date filters use UTC; displayed times use your local timezone.

Pausing stops future runs without undoing prior messages or changes. Deleting a rule retains execution history. Editing an active rule keeps it active after confirmation; pause first if you need to prepare changes without ongoing execution.

A server can hold 25 rules, paused and active combined. Checks for inactivity and follow-up records are periodic, not instant on activation. For problems, check the exact conditions, rights, channel, rule state and history before using troubleshooting.

Alert inside a private ticket

For Urgent ticket without an assignee, choose Alert in the ticket channel as the only action. Each ticket receives its own reminder in its Discord channel, without automatic mentions or copying the subject to a general channel. This option includes private categories.

Before each delivery, StaffNest checks the channel audience: @everyone must be denied viewing, and explicit viewing grants may only target the requester, bot or the ticket’s support roles. Moved channels, threads, unknown permissions or additional readers prevent sending. Discord owners and administrators keep their usual access.

Simulation counts candidate records without contacting Discord, so it does not guarantee delivery. Check run history afterward. Uncertain deliveries are not automatically repeated. The standard Notify a channel action still excludes tickets restricted to panel roles.