How Triggers Work
Every trigger has a name and a prefix. If your prefix is! and your trigger is named rules, members type !rules and the bot responds with whatever you’ve configured. Triggers can be restricted to specific roles, posted to a fixed channel, and set to delete the invoking message automatically.
Setting Up Triggers
Basic tab — core settings
Configure the essentials: - Trigger name — the word after the prefix
that activates this trigger (no spaces, lowercase only) - Message content
/ Embed description — the main text of the response. Use variables to
personalise it. - Post to channel — where the bot posts the response.
Leave empty to reply in the same channel where the command was used. -
Ping role — optionally ping a role when the trigger fires. Use
{args1}
to dynamically ping whoever is mentioned as the first argument. - Allowed
roles — restrict the trigger to members with specific roles. Leave empty
to allow everyone. - Enabled — toggle whether the trigger is active.Embed tab — rich formatting (optional)
Enable Send as embed to wrap the response in a Discord embed. Then
configure: - Accent colour — the left-border colour of the embed (hex
code, live swatch preview included) - Title and Title URL - Author
name and Author icon URL - Thumbnail URL (top-right image) -
Image URL (full-width image) - Fields — up to 25 key/value pairs,
each optionally inline - Footer text and Footer icon URL -
Timestamp — appends the current time to the footer
Advanced tab — behaviour options
Fine-tune how the trigger behaves: - Cooldown — seconds between uses per
user (0 = no cooldown) - Delete response after — seconds until the bot’s
response is auto-deleted (0 = never) - Delete invoking message — removes
the member’s command message after the bot responds - ModMail enabled —
allows this trigger to be used inside ModMail thread channels
Preview tab
Switch to the Preview tab to see a Discord-style rendering of your
trigger response before saving.
Available Variables
Click any variable pill in the editor to insert it at your cursor position.| Variable | Output |
|---|---|
{user} | Mentions the user who used the trigger |
{username} | Their Discord username |
{avatar} | Their avatar URL |
{server} | Your server’s name |
{channel} | Mentions the current channel |
{everyone} | @everyone |
{here} | @here |
{&rolename} | Mentions a role by name |
{#channel} | Mentions a channel by name |
{date} | Current date (MM/DD/YYYY) |
{time} | Current time (XX:XX:XX) |
{datetime} | Date and time combined |
{timestamp} | Unix timestamp ID (wrap with <t:ID:?> for Discord formatting) |
{year} | Current year |
{month} | Current month |
{day} | Current day |
{args1} | First word after the trigger name |
{args2} | Second word after the trigger name |
{args3} | Third word after the trigger name |
Configuring the Prefix
All triggers in a portal share a single prefix. To change it:- Click the Prefix button in the top-right corner of the Triggers page (Owners and Admins only).
- Edit the prefix field — it must be 1 to 5 characters.
- Click the confirm button to save.
Managing Triggers
Each trigger card shows the full command name, a preview of its description, and any configured constraints (channel, cooldown, allowed roles).| Action | Description |
|---|---|
| Toggle | Enable or disable the trigger without deleting it. |
| Edit | Update any setting, including the trigger name. |
| Duplicate | Creates a copy of the trigger. The copy is pre-filled with the same settings — the name is suffixed with copy and must be renamed before saving. |
| Delete | Permanently deletes the trigger. |
Access Control
Viewing and using the Triggers page can be granted to non-admin staff via the Permissions system using theCanView permission on the Triggers page. Creating, editing, and deleting triggers may require additional permissions depending on your portal’s configuration.