All integrations

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.

Capabilities

What agents do with Discord

Helios vector-searches the Discord API surface at run time, so an agent reaches for whichever endpoint the task needs.

  • 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.

Use cases

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.

Daily at 7:00pm

Every evening, summarize community activity and list unanswered questions.

  1. discord·read 6 channels from the last 24h
  2. code·cluster topics and find unanswered threads
  3. 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.

Every 2 hours

File clear bug reports from #help as GitHub issues.

  1. discord·read new #help threads
  2. github·search for an existing issue
  3. github·open issue with repro steps
  4. 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.

Every 15 minutes

Answer questions in #help that our docs already cover.

  1. discord·read unanswered #help messages
  2. notion·search docs for a match
  3. 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.

github · release.published

On each release, post community-friendly notes to #announcements.

  1. github·read release notes for v2.8.0
  2. discord·post embed to #announcements

v2.8.0 announced

  • Rewrote three internal terms into plain language
  • Called out the one breaking change up front

Cross-app recipes

Discord works alongside the rest of your stack

One agent, one run, several services. It reads from one tool and writes to the next without a handoff.

FAQ

Questions, answered

Put an agent on Discord.

Connect it once, describe the task in plain English, and let it run on your schedule or your events.