Actions32
- Analytics Actions
- Moderation Actions
- Backup Actions
- Automation Actions
- Insights Actions
Overview
This node provides advanced analytics for Discord servers, specifically focusing on the 'Top Contributors' operation within the 'Analytics' resource. It identifies the most active contributors in a Discord guild by analyzing message activity across all text-based channels over a specified time range. It supports filtering options such as including or excluding bot activity, minimum message count thresholds, and limits on the number of contributors returned. This node is useful for server administrators or community managers who want to recognize and engage their most active members.
Use Case Examples
- A community manager wants to identify the top 10 most active users in their Discord server over the past 7 days to reward them.
- A server admin wants to analyze user engagement by excluding bot messages and focusing on users with at least 5 messages in the last month.
Properties
| Name | Meaning |
|---|---|
| Guild ID | The ID of the Discord server (guild) to analyze. |
| Time Range (Days) | The number of days to analyze message activity, ranging from 1 to 30. |
| Additional Options | Optional parameters to customize the analysis, including whether to include bot activity, minimum messages for analysis, whether to include attachment data, spam threshold, inactive days, and maximum items to process. |
Output
JSON
guildId- The ID of the Discord server analyzed.timeRange- The number of days over which the analysis was performed.topContributors- An array of the top contributors, each containing userId, username, messageCount, channelCount, and channels (list of channel names where the user was active).totalAnalyzed- The total number of unique users analyzed in the guild.
Dependencies
- Discord API access via a bot token credential
Troubleshooting
- Ensure the provided Guild ID is correct and the bot has access to the guild.
- The bot must have permissions to read messages and fetch members in the guild.
- If the channel or guild is not found or not accessible, the node will throw an error.
- Large guilds or channels with many messages may cause rate limiting or timeouts; consider reducing the time range or max limit.