Automatically enabled when you configure Discord permissions in your agent workflow.
What It Does
- Post a message in a channel, a thread or a forum, with embeds, mentions and files, and edit or delete it
- Send a person a direct message about a ticket
- Post an approval request, add ✅ and ❌ reactions to it, and on a later run or turn read who reacted or replied, counting only the approvers your instructions name
- Read and search messages, replies, reactions, pins and threads
- Find servers, channels, members and roles by name
- Create, change and delete channels and threads; time out, kick and ban members; give and take roles; create invites; schedule server events
- Read the server’s audit log, its webhooks and the bot’s own application
Approvals in Discord
Discord answers an approval request with a reaction or a reply, which the agent reads on its next run or turn. Neo does not wait inside a run for it, and Neo does not receive clicks on Discord buttons. The agent writes the request’s channel and message ids in an internal note on the ticket, so the next run finds it, and acts only when an approver your instructions name has approved and none has declined. This is a decision your team makes in Discord. A write your agent’s permissions mark as needing a technician’s approval still asks for it through Neo’s own approval step.Permission Groups
A member update that sets roles, and a channel change that sets permission overwrites or syncs them with the category, need Roles & Access, whatever path they use.