Discord icon

Discord

Interact with Discord API - Full Bot Features
Join our community

Actions53

Overview

This node interacts with the Discord API to perform various operations related to Discord messages. Specifically, the 'Get' operation under the 'Message' resource fetches a specific message from a given channel by its ID. This is useful for retrieving message details such as content, author information, timestamps, and edit status. Practical applications include automating message retrieval for logging, monitoring, or processing message content within Discord channels.

Use Case Examples

  1. Retrieve a message by its ID to analyze its content or metadata.
  2. Fetch a message to display its details in an external dashboard or system.

Properties

Name Meaning
Channel ID The ID of the Discord channel from which to get the message.
Message ID The ID of the specific message to retrieve from the channel.
Additional Fields Optional extra parameters that can be used for other operations but are not specifically used in the 'Get' message operation here.

Output

JSON

  • id - The unique identifier of the message.
  • content - The textual content of the message.
  • author
    • id - The unique identifier of the message author.
    • username - The username of the message author.
    • bot - Boolean indicating if the author is a bot.
  • channelId - The ID of the channel where the message was posted.
  • createdTimestamp - Timestamp when the message was created.
  • editedTimestamp - Timestamp when the message was last edited, if applicable.

Dependencies

  • Discord API
  • Bot token credential for authentication

Troubleshooting

  • Ensure the provided Channel ID corresponds to a valid and text-based Discord channel; otherwise, the node will throw a 'Channel not found or not text-based' error.
  • Verify that the Message ID exists within the specified channel; fetching a non-existent message will cause an error.
  • Check that the bot token credential is valid and has the necessary permissions to read messages in the channel.
  • Invalid JSON in embed fields (if used in other operations) will cause errors; ensure JSON is correctly formatted.

Links

Discussion