Managing a Discord community means staying on top of dozens of channels, spotting questions that need answers, and keeping members engaged. It's a lot of reading.
Companion reads it for you, surfaces what matters, and helps you respond faster.
What you need
- Companion installed (download here)
- An OpenRouter API key (free, pay per use)
- A Discord account with access to the server you want to manage
Step 1: Connect Discord
Open Settings → Integrations in Companion's sidebar. Find Discord and click Connect.
Authorize via Discord OAuth. You'll select which servers Companion can access. It requests read access to message history and the ability to post messages on your behalf.
Step 2: Your first automation
The most valuable starting point for community managers:
Summarize the last 24 hours of messages in #general and #support on my Discord server. What are the most common questions? Is there anything that needs a moderator response?
Companion reads both channels and gives you a prioritized digest — what's being discussed, what needs attention, and what can be ignored — without you scrolling through hundreds of messages.
Or for posting announcements:
Post a message to #announcements on my Discord: "We just shipped version 2.4 of Companion. Check the #changelog channel for details. Download link in the description."
Companion posts it. It comes from your account, in the channel you specified, exactly as written.
What it costs
Reading a day of Discord messages uses roughly 2,000–8,000 tokens depending on server activity. At Claude Haiku rates via OpenRouter, a busy server digest costs about $0.002–0.008. For a moderately active community, a full month of daily digests costs under $0.50.
More workflows
Support triage: "Check #support for any questions posted in the last 48 hours that haven't received a reply. List them with the username and question."
Welcome new members: "Check #general for any new members who joined in the last 24 hours and haven't said anything yet. Draft personalized welcome messages for each one."
Community insights: "What topics are being discussed most in my server this week? Are there any recurring complaints or feature requests?"
Cross-post announcements: "Take the announcement we just posted on Discord and format it for Twitter/X and LinkedIn. Keep the tone consistent."
Event promotion: "Post a reminder to #events that our weekly community call is tomorrow at 6 PM UTC and include a Google Meet link"
For product teams, combining Discord with GitHub means you can surface bug reports from the community and automatically create GitHub issues — one prompt bridges the conversation to the backlog.
Achmad Bifari is Creative Designer and Social Manager at Companion. He writes the tutorials and runs @companionbyaios.