Messaging
Discord
A Discord integration connects a Discord bot token to Mobius so loops can inspect guilds and channels, send messages, update threads, and manage reactions.
Use Discord when run output belongs in a Discord community or when a loop needs to read recent channel context before replying. Discord does not currently register source events in Mobius, so it is an action provider, not a trigger source.
Capability map
| Capability | Value |
|---|---|
| Provider ID | discord |
| Auth kind | api_key |
| Connect flow | Inline bot token |
| Actions | Yes |
| Events | No |
| Webhook delivery | No |
| Event samples | No |
| Live status | Yes |
Connect Discord
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose Discord, and paste a bot token. |
| CLI | The mobius CLI does not connect Discord integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/discord/connect with the Discord credential body from the API reference. |
After connecting, run the live-status check from the app or API if actions report missing guilds or channels. The bot must be invited to the server and granted the permissions each action needs.
Actions
discord.channel.get
discord.channel.list
discord.guild.get
discord.guild.list
discord.message.delete
discord.message.get
discord.message.history
discord.message.send
discord.message.update
discord.reaction.add
discord.reaction.remove
discord.thread.createUse read actions to resolve guild and channel IDs before sending messages.
Guard discord.message.delete with an interaction when the deletion depends on
agent judgment.
Events
Discord does not register source events yet. Start runs with a schedule, HTTP trigger, or another provider event, then call Discord actions inside the run.
Next
- Add deterministic work with action steps.
- Check provider readiness from integrations.
- Use source events for providers that can trigger runs.