Weekly Discord community pulse digest

Every Monday at 9am, run a community pulse agent for our Discord server.

The trigger is cron (weekly, Monday 09:00 in the server owner's local timezone). Let the user configure two things at setup: a list of channel IDs to sweep (e.g. #general, #help, #showcase, #feedback) and a single announcements channel ID to post the digest into.

For each configured channel, use Discord's Get Channel Messages to fetch the last seven days of messages. Cap reads at roughly 200 messages per channel to stay within the 100-per-page pagination (fetch a first page of 100, then a second page using the last message's id as the `before` cursor). Stop paginating once you hit a message older than seven days. Collect author, timestamp, content, and reply/reference context for each message.

Then reason over the raw messages across all channels to pull out four things: (1) the top 3–5 trending topics or themes the community was talking about, (2) the most-asked unanswered questions (messages that looked like questions and got no meaningful reply), (3) standout contributors worth shouting out (members who helped others, shared great work, or drove good conversations), and (4) any product or community wins members shared (launches, milestones, cool demos).

Then use Discord's Send a Message to post the digest into the configured announcements channel as a rich embed. Use the Discord Blurple brand color (0x5865F2). Structure it as embed fields: one field per section (Trending topics, Unanswered questions, Community shoutouts, Wins of the week), with each item as a short bullet including a channel mention and, where useful, an @mention of the contributor. Add a short intro line in the embed description and a footer like "Community pulse • last 7 days". Respect Discord's 6000-character total embed cap and the 25-field / 1024-char-per-field limits — if content overflows, trim the least important bullets first.

Finally, use Discord's Pin a Message on the message that was just sent so the digest stays visible in the announcements channel for the week. If pinning fails because the channel already has 50 pins, log the failure but do not retry, and still consider the run successful.