Actions are used to perform various operations in response to a command or component invocation.
Actions are part of Custom Commands.
Each action has a certain set of general settings regardless of its type:
Action Name — the name of the action displayed in its tab and action selections;
Action UUID ("i" icon) — unique action identifier used in Message Templates;
Action Type — type of the action. You can find detailed explanation for each of them just below in next sections within this category;
Short description — just a short description of this action displayed in action selections;
Override Access Rights — turning on this option will force access rights checking for this action additionally to command's access rights.
Send Message — execution of such action will result in simple response with specified text or embed.
Modal Form — execution of such action will show modal form to get some input from user with great UI.
Change Roles — execution of such action will remove or add the roles specified in the action settings. By default, this can only be done by the member who executed this action by command or component.
Internal Command — execution of such action will be redirected to build-in command specified in the template of this action. For example, if you create a command with the name
me, enter the
userin the action template, invocation of
!mecommand will do the same thing as you would invoke
Executing action by another action#
If you're an advanced used able to handle advanced features of Message Templates,
you can use
run tag to run action from another action.
More detailed information about how to do it is described here.
Message Components have all parameters that were available for its own message template including newly stored parameters. It means that action executed by message component will get the same parameters that parent message template had.
Parameters lifecycle is limited to 15 minutes from the moment when they were accessed last time!