Direct Message a User
While the Direct Message a User action block is still available for use in all commands and events, it is considered old and has been replaced by the Send or Edit a Message action block. We advise you to use the Send or Edit a Message block instead, which offers more functionalities and possibilities for your message.
When triggered, the Direct Message a User action responds with a DM to a user of your choosing. This message can either be sent to the user who triggered the block, a user option, or a user ID. All variables and options can be used in the content of the reply.
User to DM
To receive a direct message, the user must have Direct Messages enabled.
The Direct Message a User action has three options that change to whom the message of the action is sent. Below you can find detailed information about each option and how it can be used.
By selecting this option your Direct Message will be sent to the user who used the most recent interaction; for example, the most recent button press, select menu choice, command run or the user who triggered the custom event.
Message
In the Direct Message a User action, you have the choice for each message to be plain text, or an embed.
Reactions
Reactions can also be added to the reply. These can be added by clicking the reactions dropdown and selecting emojis.
These reactions will be automatically added to the reply.
Optional Variable
You can also create your own variable that can be used anywhere in the command to get the ID of the message sent by the action. This is useful when using Send an API Request in your command / event and you need the ID of the message. Make sure that the name of the variable does not correspond to the name of a default variable or of an another action.
You can copy the variable by clicking the clipboard icon in the section right below the optional variable field.
Last updated