find the decision halfway down a teams thread
bring the decision to the next meeting, even when it sits twelve replies below the original proposal. give a dusk bot the microsoft teams thread and ask who agreed to what.
it can read replies, compare them with an available meeting transcript and return the lines that settle the question in your dusk chat.

what a bot can do in Microsoft Teams
name the place where people actually answered. a channel post, a chat pin and a meeting transcript each have a different id. start with the one that holds the decision. use the others when the team needs to reconcile two versions.
| action | dusk bot treats it as | what you would use it for |
|---|---|---|
| Get Teams channel message | read | open the proposal at the top of a known channel thread |
| List channel message replies | read | read what colleagues accepted or changed in later replies |
| List pinned messages | read | collect instructions pinned in a particular chat |
| List meeting transcripts | read | find transcript records available for the meeting you named |
| Get meeting transcript content | read | read the words behind a disputed meeting note |
| Send Channel Message | send: asks first | publish a reviewed announcement as a fresh channel post |
composio, the connection service behind dusk bot's apps, lists 253 Microsoft Teams actions (version 20261120_00, read 20 november 20264). dusk bot treats 127 as reads, 7 as sends and 119 as changes.
only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like reply to teams channel message, and waits for your Allow unless you set a daily amount.
connect Microsoft Teams
- open Connected apps in the sidebar.
- pick Microsoft Teams and sign in on Microsoft Teams's own page, so your password goes to them and never to a bot.
- choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your Microsoft Teams.
- ask in plain words. reading and drafting happen freely; sending asks you first.
give the bot the team, channel and parent message ids for a recurring discussion. connect microsoft teams in connected apps and allow the named read actions. for a chat pin review, give it the chat id instead. channel replies belong to their parent post. put the planning call’s online meeting id in the bot’s job.
routines to copy
agree on what counts as a decision. some teams use an owner’s yes. others need a date and a named person to act. tell the bot which evidence to bring back.
decisions in the launch thread
at 4 each weekday, open our launch thread in teams. read the original message and every page of replies. list decisions made today, the person who agreed and the line that confirms each one. leave suggestions under open questions here.weekdays at 4 pm · confirmed decisions with the replies that support them
meeting promises
every thursday at 3, read the available transcript for the planning call whose online meeting id is in your job. pick out promises people made in their own words. show the speaker and deadline when the text gives them. bring me any unclear ownership. do not post minutes.thursdays at 3 pm · commitments for the meeting organizer to confirm
instructions pinned in chat
every monday at 9, read all pinned messages in our operations chat, including their text. find any that name a date already past. quote the instruction and date here so i can decide whether to keep the pin. leave the pins alone.mondays at 9 am · pinned instructions with dates worth revisiting
what it asks you first
keep the decision note in dusk until someone chooses its audience. posting a channel message asks first by default. the post action creates a new top-level message. it will not put the note under the proposal. editing an existing channel message is a change and has no send prompt.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
what it cannot do
- retrieve a transcript that the meeting does not have. the transcript content action needs a calendar-backed online meeting with an available transcript.
- read a whole channel thread from its parent alone. replies have their own action. it can take several pages to reach the last one.
- start a routine the moment a teams reply lands through this connector. choose a review time or ask in dusk when you need the answer.
when the team still disagrees
a summary cannot break a tie. if the replies contain two different launch dates, give the owner both lines. if you need a decision in a live conversation, ask the people in teams. use the bot to recover the record once the discussion has moved on.
what it looks like
a fictional example.
before
helen cross proposed tuesday in the first channel post. later she agreed to thursday after the installer changed dates.after the bot
agreed date: thursday. helen confirmed it in the later reply. tuesday was the initial proposal.an illustration with made-up names and numbers.
questions
will this bot join our meeting to take notes?
the transcript routine reads a transcript after one exists. give it a supported meeting id. if there is no transcript to read, it should say so.
does a pinned message belong to a channel or a chat here?
the pin lookup takes a chat id. give it the operations chat for that routine. a channel thread needs the team, channel and parent message instead.
sources
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].
turn meeting notes into a decision log
find the instruction that changed in a confluence runbook
a slack assistant that finds the decision in the thread
add new airtable rows without rewriting existing records
turn your notes into a comment on the right asana task
ask what an asana task actually says