Starts with a slash command and the message menu
Warnings and reports
/warn counts the warnings per member and sends them the reason by DM. Everyone else gets Report to mods in the right-click menu of a message, and the report arrives in your mod channel with a link.
Illustration. The real interface may look different.
How it works
/warn takes a member and a reason, adds one to their warning count and sends them a DM.
If the DM can't be delivered, the mod who used /warn is told.
Report to mods, in the Apps menu of a message, posts a link to that message in your mod channel.
The reporter gets a thank-you only they can see.
How to make a /warn command and message reports on Discord
Two small flows. /warn keeps one number per member. The report stores nothing: it turns a right-click into a post your team can act on.
Describe it to your AI assistant
My mods keep losing track of who has already been warned. Build two flows. First: /warn with a user and a reason, usable only by members with the Time out members permission. It counts warnings per member, DMs them the reason and tells the mod if the DM could not be delivered. Second: a "Report to mods" entry in the right-click menu of messages, with a 30 second cooldown per member. It posts the reporter, the author, the first 300 characters and a "Jump to message" link button in #mod-reports and thanks the reporter privately.
Copy it and swap in your own channel and role names. Your assistant has a tested version of this example to start from.
Build it in the editor
Two flows that do not depend on each other: /warn on a "Slash command" trigger and "Report to mods" on a "Message context menu used" trigger. In the "Create new flow" dialog, "Start from a template" offers the first as "/warn command".
The 2 flows, step by stepStep names are the ones the editor shows.
Flow 1/warn
Trigger: Slash command/warn with the options user and reason.
- Fetch member by IDFetches the member named in the command.
- Increase a stored numberAdds 1 to their warning count and hands back the new total.
- TryWraps the DM, so a member with closed DMs does not break the command.
- Send DM to memberSends the member the reason by DM.
- Follow up to interactionIf the DM failed, tells the moderator privately.
- Reply to interactionConfirms the warning with the member's new total.
Flow 2Report to mods
Trigger: Message context menu usednamed "Report to mods", with a 30 second cooldown per member.
- Build message linkBuilds a link to the reported message.
- Truncate textCuts its text to 300 characters.
- Create messageBuilds the report: who reported, whose message, the quote and a "Jump to message" link button.
- Send messagePosts it in your mod channel.
- Reply to interactionThanks the reporter, visible only to them.
Test it, change it
What it stores
- WarningsPer userOne number per member. Reports store nothing.
How to test it
- Open a flow in the editor and click "Test run". Choose the member under "Run as" and click "Run test". The run uses your real server data but sends, changes and deletes nothing, and shows what each step would have done.
- A new flow is a "Draft" and does not run in Discord. Switch it on and click "Save & activate".
- Warn a second account in Discord and check the DM and the count. Then right-click any message, choose Apps and "Report to mods", and look in your mod channel.
- Each real run then shows up under "Executions", with the reason if it failed or was skipped.
What to change
- Who can warn
- "Required permissions" on the /warn trigger. Set it before you activate the flow.
- Report channel
- Picked in the "Send message" step of the report flow.
- Wording
- The DM and the confirmation are in the two "Create message" steps of /warn.
- Menu name
- "Command name" in the report trigger. It is what members see under Apps.
Watch out for
- The dashboard template for /warn has no required permission set, so every member could use it. Set "Required permissions" on the trigger first.
- Warnings are a count. The reasons go out by DM and are not kept, so ask for a stored list if you need a history.
- Anyone who can see a message can report it. The cooldown keeps one member from flooding your mod channel.
Questions about this build
How do I see how many warnings a member has?
Every /warn answers with the member's new total. For a look without warning anyone, open "Stored data" in the dashboard, or add a small /warnings command that reads the count.
Can I remove a warning?
Yes. Edit the member's number under "Stored data", or build an /unwarn command that lowers the count by one.
Can the third warning time a member out automatically?
Yes. After the count is raised, add "If" for your limit and "Time out member". Your bot needs the "Time out members" permission for it.
More examples
- 21:14Staff applicationsAn /apply form for applicants, Approve and Deny buttons for your team.staff-applications
- 13:05SuggestionsMembers post ideas, everyone votes, and your mods get a ping when one takes off.suggestions
- 16:48Simple ticketsA button opens a private thread with your team, and /close archives it.support
Szeretnéd a szervered a bétában?
A V3 nagy rendszer, és még gyorsan változik, ezért a szerverek egyesével érkeznek, nem egyszerre. Minden jelentkezést ember olvas el, és pár napon belül visszajelzünk.
A bétában lévő szerverek döntik el nagyrészt, mit építünk legközelebb. Amit megépítesz, az a tiéd: a flow-k és a modulok a béta végén is megmaradnak.