an excel bot for the workbook you actually mean

what a bot can do in Excel

the excel toolkit is composio's microsoft excel connection. its workbook actions are separate from giving a bot a local attachment. choose a connected workbook for ongoing app work, or attach the .xlsx when the job is about that file.

composio, the connection service dusk bot uses for apps, lists 125 Excel actions (catalog version 20261103_00, read 12 november 2026⁴). dusk bot treats 60 of them as reads, 1 as sends and the other 64 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 create comment: it waits for your Allow unless you've given that bot a daily amount it may send alone.

connect Excel

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

for connected work, choose excel in Connected apps, finish microsoft's sign-in and allow the workbook bot to use it. identify the file and sheet before asking for an edit.

for a file task, drop the .xlsx into chat or use Attach files. tell the bot what to inspect and ask for the result as a file in chat. it can also use a project folder you give it.

routines to copy

start with a workbook review that leaves values alone. add a write job only after the bot has correctly identified the sheets and columns.

every monday at noon, read the budget and actual columns in the acme planning workbook. list the largest differences, showing both inputs and the row label. keep different currencies separate. do not update formulas, values or formatting.

every wednesday at 9, inspect the allocation table in the acme staffing workbook. flag rows with a missing person, week or assigned hours. report the row reference and missing field. leave the table order and all entries alone.

on the last day of each month at 3, find the acme monthly workbook and confirm its sheet names with me. ask me before you change anything or export it. after i agree, make a pdf for my review and put the result in this chat.

what it asks you first

connected workbook edits use app permissions. updating cells or adding charts is not documented as pausing for a sending card. limit the bot to a narrow set of excel actions, and write "ask me before you change anything" when the job needs a checkpoint.

file work uses the bot's computer permissions instead. start on Ask for approval while you inspect how it handles a dropped workbook. these are different controls from the separate setting for sends such as emails and messages.

what it cannot do

• change a connected excel range under read-only access. a report in chat can stay separate from workbook writes.
• run this connection as a local workbook-change event feed. composio lists no excel events, so the routines here run on a schedule instead.
• open the desktop app and carry out a scheduled workbook job while your machine is sleeping. local work pauses then; use an always-on bot machine if the timing matters.

make the file route explicit

say "review this attached workbook and return your findings here" for a one-off .xlsx. for an ongoing report, give the connected file reference each time. do not let a familiar filename stand in for the source: ask which workbook and sheet the bot read. google sheets uses a separate connector.

decide where the report belongs

a generated file appears in chat and lives in the bot's folder or project folder. think about that destination before building a file organisation routine. if you later want to email the report through outlook, that is another connection and the send has its own approval setting.