Create and use a saved message
Owners and admins with Community & Discord access can manage templates in Discord > Messages. Connect the intended server first and ensure the bot can view and send messages in the test or delivery channel.
- Choose New, enter a Name and select Template type for the feature that will use it. For ticket and role panels, choose Ticket Panel or Role Panel respectively.
- Write Message content, an embed, or both. Add optional embed fields, images and footer details in the existing editor.
- Under Buttons & dropdowns, configure controls only when needed. A Link button needs a URL. Generic non-link buttons and dropdowns remain disabled unless a supported feature supplies their behavior; adding a button does not invent a new bot action.
- For a configurable button, leave Emoji (optional) empty for text only. Supply a Unicode or custom Discord emoji for emoji plus text, or leave Label empty with a valid emoji for emoji only. Choose Primary, Secondary, Success, Danger or Link; arbitrary button colors are not available.
- Set Default channel and Mention policy deliberately. Add variable defaults where the target workflow cannot supply a value.
- Click Save, then Preview. Review unresolved variables and correct their values before delivery. Emoji variables may remain unresolved in preview; actual delivery requires valid resolved emoji values.
- Choose a test channel through Default channel and use Test send. This posts a Discord message; it is not a dry run. Use a staff channel if the copy is not ready for members.
- Select the saved template in the consuming feature, such as Tickets or Onboarding, and use that feature's publish action to attach its actual controls.
Edit and apply changes
Select the existing template, edit it and click Save. Saving a template does not automatically rewrite every previously posted Discord message. Use Update panel for Tickets, Update Discord Message for Self-Role Panels, or Refresh now for a sticky after editing its template. Other consumers render the saved copy on their next send unless their own workflow offers an update action.
Troubleshooting
If a template is missing from a feature's picker, check the workspace and Template type. If delivery reports unresolved variables, provide defaults or use variables supplied by that workflow. A preview with sample values does not prove a live event will supply those values. If a custom emoji renders in the dashboard but Discord rejects it, check that the bot can use it.
Feature reference
Message Builder is the reusable customer-controlled message system used by Community & Discord.
The important rule is that community-facing copy is not permanently hard-coded into Brainer. A workspace can write and save the message it wants Brainer to send.
Templates can include:
- normal message content
- embed title
- embed description
- embed color
- author name and icon
- thumbnail
- image
- footer and footer icon
- embed fields
- buttons
- link buttons
- select menus
- default Discord channel
- mention policy
- variable defaults
Current template types include:
- Welcome
- Verification
- Rules
- FAQ
- Official Links
- Role Panel
- Ticket Panel
- Raid Alert
- Moderation Alert
- Community Report
- Community Alert
- Guard Alert
- Custom Command
- Scheduled Announcement
- Custom
Preview and test send
The Messages page can render a preview and send a test message to Discord. Generic previews disable interactive non-link controls until a feature such as verification, role panels, or tickets binds the action.
Variables
Templates can use dynamic variables such as:
- {{member.name}}
- {{member.username}}
- {{member.mention}}
- {{member.account_age}}
- {{member.created_at}}
- {{member.joined_at}}
- {{server.name}}
- {{server.member_count}}
- {{role.name}}
- {{ticket.number}}
- {{ticket.category}}
- {{moderator.name}}
- {{community.active_members}}
- {{community.total_members}}
- {{community.new_members_7d}}
- {{community.new_members_30d}}
- {{community.rejoins_30d}}
- {{community.leaves_30d}}
- {{community.net_growth_30d}}
- {{community.retention_7d}}
- {{community.retention_30d}}
- {{community.activity_change_pct}}
- Community alert variables
- Guard incident variables
Setup commands such as /setup-welcome, /setup-verify, /setup-rules, /setup-faq, /setup-official-links, /setup-tickets, Community Health reports, Guard alerts, and custom commands use saved customer content where supported.