Triggers are prefix-based commands that the Invaro bot responds to with a custom message. When a server member types your configured prefix followed by a trigger name, the bot posts the associated content — a plain message, a rich embed, or a combination of both. Triggers are ideal for frequently posted information, staff commands, or server-specific quick replies.Documentation Index
Fetch the complete documentation index at: https://docs.invaro.org/llms.txt
Use this file to discover all available pages before exploring further.
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 — the main text of the response when not using an embed. Use
variables to personalise it. If embed mode is enabled, this field becomes
plain text above embed — optional text that appears above the embed as a
regular message. - Post to channel — where the bot posts the response.
Leave empty to reply in the same channel where the command was used. -
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) - Embed description — the main body
text inside the embed - Ping role — optionally ping a role when the
trigger fires. Use
{args1} to dynamically ping whoever is mentioned as the
first argument. Only available when embed mode is enabled. - 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 footerAdvanced 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
Flows tab — automated actions (Invaro+ only)
Add Custom Flows to chain additional bot actions that fire automatically
after the trigger runs. See Custom Flows below for full
details.
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 |
Custom Flows
Custom Flows are available on Invaro+ and Invaro+ Boost portals only.
Available Flow Actions
| Flow | Description |
|---|---|
| Move channel to category | Moves the channel the trigger was run in to a different category |
| Delete previous bot message | Deletes the bot’s last message in the channel before sending the new response |
| Send DM to invoker | Sends a direct message to the user who invoked the trigger |
| Send DM to mentioned user | Sends a DM to a user mentioned as the first argument — requires !trigger @user |
| Pin bot response | Pins the bot’s response message in the channel |
| Add / Remove roles | Adds or removes one or more roles from the user who invoked the trigger |
| Create thread on response | Creates a public thread directly on the bot’s response message |
| Create thread in channel | Creates a standalone thread in the channel, independent of the bot’s response |
Adding a Flow
- Open a trigger and navigate to the Flows tab.
- Click any action in the Add a flow action grid to add it. Each flow type can only be added once per trigger.
- Configure the flow-specific options that appear (see below).
- Save the trigger. All enabled flows will run in order when the trigger fires.
Flow Configuration Options
Move channel to categorySelect the target category from the dropdown. The channel the trigger was invoked in will be moved there automatically.Send DM to invoker / Send DM to mentioned user
Choose whether the DM should mirror the trigger’s response or contain a custom message:
- Send trigger response — the bot DMs an exact copy of the trigger’s embed and plain text.
- Send custom message — write a separate message for the DM using the text editor and variable pills.
For Send DM to mentioned user, the trigger must be invoked asAdd / Remove roles!triggerName @user. If no user is mentioned, the flow is skipped. Use{args1}inside the custom message to reference the mentioned user.
Select whether to Add or Remove roles, then pick one or more roles from the dropdown. The selected roles are applied to the user who invoked the trigger.Create thread on response / Create thread in channel
Set a thread name (variables supported) and choose an auto-archive duration:
| Duration | Archives after |
|---|---|
| 1 hour | 60 minutes of inactivity |
| 24 hours | 1 day of inactivity |
| 3 days | 3 days of inactivity |
| 1 week | 7 days of inactivity |
Threads created on response are attached to the bot’s message. Threads created in channel are standalone and not linked to the response.
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.