Community
Give your agents full access to Discord.
Agents read channels, follow threads, post updates, and keep an eye on the community while your team sleeps. Give one a schedule and every question, bug report, and feature request gets captured.
5,000 free credits to start.
Agent reach
Discord API v10
The full surface, searched at run time.
Connect with
- Your own OAuth app
Create a bot in the Discord developer portal and paste its token.
Event triggers
Not yet
Manual, schedule, and signed webhook are available.
What the agent can do
What agents do with Discord
Helios searches the Discord API v10 at run time. The agent finds the endpoint the task needs and calls it.
- Search Discord's entire API surface at run time and call any endpoint your bot's permissions allow.
- Read channel messages and threads across the servers your bot has joined.
- Post messages, embeds, and thread replies.
- Manage roles, reactions, and channel membership within the bot's permissions.
- Cluster community conversation into themes worth acting on.
- Route bug reports and feature requests into GitHub or Notion.
Examples
Tasks you can hand to a Discord agent
Digest the community every day
The agent reads every channel, separates questions from noise, and posts a digest with the threads that still need an answer.
Every evening, summarize community activity and list unanswered questions.
- discord·read 6 channels from the last 24h
- code·cluster topics and find unanswered threads
- slack·post digest to #community
Community · Mar 6
- 142 messages · 4 themes
- 7 questions still unanswered, oldest 9h
- 2 bug reports worth filing
Capture bug reports as issues
When someone describes a real bug, the agent files it in GitHub with the reproduction steps and links back to the thread.
File clear bug reports from #help as GitHub issues.
- discord·read new #help threads
- github·search for an existing issue
- github·open issue with repro steps
- discord·reply with the issue link
2 issues filed
- #1194 export fails on large workspaces
- #1195 dark mode contrast on the runs table
- Both linked back to their Discord threads
Answer the common questions
The agent watches for questions it has documentation for, answers them in thread, and leaves the rest for the team.
Answer questions in #help that our docs already cover.
- discord·read unanswered #help messages
- notion·search docs for a match
- discord·reply in thread with the answer
4 questions answered
- Each reply links the relevant doc section
- 3 questions left for the team as no doc exists
Announce what shipped
When a release publishes, the agent writes the community-facing version of the notes and posts it to the announcements channel.
On each release, post community-friendly notes to #announcements.
- github·read release notes for v2.8.0
- discord·post embed to #announcements
v2.8.0 announced
- Rewrote three internal terms into plain language
- Called out the one breaking change up front
Triggers
How a Discord workflow starts
Discord does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook.
Manual
Run it from the app with an optional JSON payload. Every workflow supports this.
Schedule
A cron expression or a plain sentence such as every weekday at 9am. Times are UTC.
Signed webhook
A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes.
Works with
Discord works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on Discord.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.