Actions
Wire buttons and commands to tickets, templates, and utilities.
Actions define what happens when a member clicks a button, picks a select menu option, or runs a custom command. They are configured in the library template editor and the command editor.
Where actions are used
| Context | How it works |
|---|---|
| Template buttons | Each button on a traditional or Components V2 template runs one action when clicked. |
| Select menu options | Each option in a select menu runs its own action when chosen. |
| Custom commands | A command runs a single action when triggered — no button click required. |
Not every action works as a custom command. Actions that need a message to click (link buttons, placeholders) or replace the current message (edit message) are template-only.
Ticket actions
Open and manage support channels.
Create ticket
Let members open a ticket in a panel.
| Variant | Component | Description |
|---|---|---|
| Single | Button | Creates a ticket in one panel you choose. |
| Multiple | Select menu | Lists up to 25 panels — each option creates a ticket in that panel. |
This is the primary way to open tickets. There is no built-in /ticket create
command — add a create-ticket action to a template or command instead.
Claim ticket
Available when editing a ticket panel's creation template. Operates on the ticket channel the message was sent in.
| Variant | Description |
|---|---|
| Claim | Assigns the ticket to whoever clicked. |
| Unclaim | Releases the current claim. Optionally force lets support staff release someone else's claim. |
| Who claimed | Shows who has claimed the ticket. |
Close ticket
| Variant | Description |
|---|---|
| Close | Closes the ticket immediately. |
| Request close | Asks the other party (claimer or opener) to close the ticket. |
Ticket notes
Staff-only notes attached to the ticket — not visible to the member.
| Variant | Description |
|---|---|
| Add note | Opens a modal to attach a private staff note. |
| View notes | Shows existing staff notes. |
Claim, close, and note actions only appear in the editor when the template backs a ticket panel's creation message. Create-ticket actions are available everywhere.
Template actions
Chain library templates together or send them elsewhere.
| Action | Description |
|---|---|
| Send template | Posts a library template to a channel you choose. |
| Send template to DMs | Sends a template to the member who clicked. |
| Follow up | Replies in the same channel with another template. Can be made ephemeral. |
| Edit message | Replaces the current message with a different template. Template-only — requires an existing message to edit. |
Useful for multi-step menus, alerts, confirmations, and nested flows without creating separate commands for each step.
Utility actions
Layout and navigation helpers for template buttons.
| Action | Description |
|---|---|
| Link | Opens a URL when clicked. Link-style button only. Template-only. |
| Placeholder | A button that does nothing — useful for visual spacing or disabled-looking layout. Template-only. |
| Disabled placeholder | A button that cannot be clicked. Template-only. |
| Select menu | A generic select menu you configure with custom options, each wired to its own action. Template-only. |
Custom commands
Commands run one action directly — no surrounding message. These actions are available:
- Create ticket (single panel)
- Close, request close, claim, unclaim, who claimed
- Add note, view notes
- Send template, send template to DMs, follow up
Actions that depend on a button click or an existing message (link, placeholder, edit message, multi-panel select) are not available in the command editor.
How is this guide?