what this discord connection can actually do

what a bot can do in Discord

the useful starting point is identity: which account is connected, which servers it belongs to, and what an invite points to. these are lookup tools. their presence does not mean the bot can search the discussions inside those servers.

composio, the connection service dusk bot uses for apps, lists 28 Discord actions (catalog version 20261101_00, read 12 november 2026⁴). dusk bot treats 20 of them as reads, 1 as sends and the other 7 as changes. an action counts as a read only when its name starts with a read word like get, list or search, so a bot you allow only to read can never call the rest. a send is anything that reaches a person outside the app or moves money, like resolve invite: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Discord

1. open Connected apps in the sidebar.
2. pick Discord and sign in on Discord's own page, so your password goes to them and never to a bot.
3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Discord.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect discord and give the bot read-only access. ask it to confirm your profile first, then provide the server or template you want checked. invite resolution needs sending permission instead. this avoids building a routine around the wrong account. the sign-in takes place on discord's page; your password does not go to the bot.

routines to copy

these routines are deliberately about account housekeeping and links you supply. none depends on listening to a channel. name the servers or give the relevant template or expected linked-account list when setting one up.

on the first monday of each month at 9, list my discord servers and group their names into communities, work and unsure using the categories i gave you. show unsure entries for me to review. never leave a server or change my account.

every friday at noon, list the external connections returned for my discord account. compare them with the account list i gave you and flag any differences. leave all account settings unchanged.

every tuesday at 11, retrieve the discord server template i gave you and its server widget, if available. summarise the returned information for our onboarding review. state which lookup failed rather than filling in missing details.

what it asks you first

dusk counts resolving an invite as a send, so it waits for your Allow each time, and a read-only bot can't do it. the other checks here are plain reads. the toolkit shown here has no send-message action, so enabling write access would not turn the routines into a channel assistant. keep the connection read only for the routines here. a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so set Ask every time for it.³

the sending setting doesn't cover changes like account or application settings. to keep them supervised, give the bot read-only access or write "ask me before you change anything" into the job.³ you can disable this app for a bot without changing what the rest of your bots may use.

what it cannot do

• read a channel history, search server conversations or summarise yesterday's discussion through this toolkit. this connection has no way to read channel messages.
• send channel replies or direct messages here. this is not a way to place a conversational ai teammate inside a discord server.
• treat a missing widget result as a full server audit. a routine should report what the lookup returned and what it could not inspect.
• perform recurring checks while dusk bot is closed on your own computer. a server-list review waits for a running machine; dusk cloud is an option for scheduled work.

if you meant a chat with several bots

you can have several bots talk together in a dusk bot group chat. that conversation is separate from discord. each bot keeps its own job and permissions, and you can choose who answers.

if your actual job is reviewing work conversations, inspect the available slack actions before choosing a connector. do not assume two messaging apps expose the same tools.

make failed checks useful

ask for a clear difference between "the linked-account list changed" and "the account connections could not be retrieved". one identifies a change; the other leaves the comparison incomplete. keep the expected account list in the routine so you can tell what the bot compared.