a slack assistant that finds the decision in the thread

what a bot can do in Slack

a short message can mean something different after ten replies. give the bot a channel and a question, then let it read the conversation around each match instead of treating search hits as the whole story.

composio, the connection service dusk bot uses for apps, lists 171 Slack actions (catalog version 20261101_00, read 12 november 2026⁵). dusk bot treats 67 of them as reads, 8 as sends and the other 96 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 send message: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Slack

1. open Connected apps in the sidebar.
2. pick Slack and sign in on Slack'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 Slack.
4. ask in plain words. reading and drafting happen freely; sending asks you first.

connect slack from Connected apps and select the bot that may read it. start with one channel and reading access. slack handles its own sign-in; the password is not shown to the bot. give the channel name and any threads you want excluded before scheduling a catch-up.

routines to copy

these jobs help with three different moments: returning to a busy channel, spotting a question, and preparing a handover. send the one you need to your bot.

every weekday at 11, read yesterday's conversation in #acme-launch, including replies. list decisions, open questions and dates people proposed. distinguish proposals from agreements and link each item. report here only.

when a new slack message arrives in #acme-help, check whether it asks a product question. read its thread and tell me if a reply is still needed. suggest wording here, but do not post or react.

every friday at noon, read this week's #acme-operations discussion and pinned items. prepare a handover with unfinished work and the people explicitly named for it. mark missing owners as unknown. leave the draft here for me.

what it asks you first

sending a slack message uses the sending control. with Ask every time, you review an Allow / Deny card before a message goes out. you can instead grant a daily sending amount to that bot. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. scheduling a message for later and editing a posted message count as app changes, not sends, so they don't ask first: leave them out of the bot's allowed actions, or tell the routine to ask you before it changes anything.

channel settings and other app changes are separate from sending. for a bot that only briefs you, a read-only grant is the useful boundary: it cannot post, react or change the channel. if you later grant writes, put "ask me before you change anything" in the routine where you need supervision.

what it cannot do

• answer from messages outside the connected account's access. give it a reachable conversation rather than expecting a search to reveal every discussion in the company.
• write a slack reply with reading access alone. a draft in your dusk chat is still possible; posting needs the app action and the sending permission.
• monitor overnight from a desktop that has gone to sleep. slack events arrive at once, but the bot still needs a running machine to do its work. dusk cloud keeps routines running.

ask for the message behind the claim

a useful digest lets you open the source conversation. ask for message links and separate what was decided from what was merely suggested. for a reusable channel-only version, see the slack channel digest. keep sensitive channels outside the brief unless you need them.

hand off only what belongs elsewhere

discussion may point to work in github or a decision page in notion. ask for those references in the summary. connecting another app is a separate step; reading a slack link does not give a bot access to the linked workspace.