Marketing
Discord community digest
Reads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.
The prompt
This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
Every evening at 7pm, read the last 24 hours of messages across our Discord server. Write a digest for #community in Slack: how many messages, the main themes people discussed, and every question still unanswered after two hours, oldest first, with a link to each. Then look for messages that describe a real bug with enough detail to reproduce. For each one, search our GitHub repository for an existing issue. If none matches, open an issue with a clear title, the reproduction steps as the reporter described them, and a link back to the Discord thread. Reply in that thread with the issue link so the reporter knows it was heard.
Trigger
What starts this agent
Example output
What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Community · Mar 6
- 142 messages · 4 themes
- 7 questions unanswered, oldest 9h
- 2 bug reports filed as issues
New to Helios? Start with Run your first agent.
Related templates
Pair it with these
Marketing
Reddit brand monitor
Sweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
Support
Documentation freshness audit
Checks your written docs against the actual codebase every month and comments on the pages that have gone stale.
Run Discord community digest on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.