dusk botmake a real excel table from the range you choose
turn the pasted cells into a proper excel table without typing them again. a bot wraps the existing range in a table.
give it the workbook, sheet and cells, then say whether the first row holds column names. you get the same data in a table, with the report title and footnotes left outside.
what it does
the table should start at your column names and end at your last record. the bot finds the workbook in onedrive and reads the cells first. it creates a table over existing data; it adds no new rows.
name the sheet and range, such as a1:d4 on intake. say whether that first row contains headers. that keeps a real record from becoming a heading.
when you would use it
- tidy a visitor log. turn its entries and column names into a table.
- prepare pasted orders. turn the existing cells into a table before sharing the workbook.
- keep the title outside. start a supplier contact table below the report heading.
try it
paste this into a chat with your bot
on the first monday of each month at 10, inspect the new monthly intake sheet in the cloudbridge permits workbook.
- show the proposed range around intake columns only
- say whether its first row contains headers
- ask me before you change anything
after i agree, create the table and report the sheet and range here. exclude notes beneath the data. leave cell values alone. if a table already exists there, stop instead of making another.- when
- first monday of the month at 10:00
- needs
- excel connected with read and write; access to the cloudbridge permits workbook
what comes back looks like this (an example)
cloudbridge permits
sheet: november intake
range: a3:e18
headers in the first selected row: yes
notes below row 18 stay outside.
proposed table: november intake, a3:e18. approve that range to create it.set it up
- allow table creation. connect excel with read and write for this bot.
- find the workbook. give its name and have the bot show which sheet it found.
- draw the boundary. ask for the range and header choice before creation.
- inspect the result. open the workbook after creation. pause the monthly job if its layout changes.
what it needs from you
| input | required | what it is |
|---|---|---|
address | yes | The range address for the table. |
item_id | yes | The ID of the Excel workbook (drive item) where the table will be created. |
hasHeaders | yes | Whether the first row of the range contains column headers (True) or not (False). |
drive_id | no | Optional drive ID. |
worksheet | no | Worksheet name or ID. |
session_id | no | Workbook session ID controlling persistence. |
from composio's catalog for Excel (action EXCEL_ADD_TABLE, read 12 november 20264). your bot fills these in from what you tell it.
how dusk bot handles it
dusk bot counts Add Table as a change: it alters something in Excel, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Excel asks for to run it: Files.ReadWrite.
where it stops
- cells need a sheet. name it separately or include it in the range address.
- start below the report title. the first table row should contain column names or data, as you chose.
- use a separate import to add rows. table creation wraps the cells already there.
- keep creation behind your go-ahead. the sending rule does not cover tables; the routine above tells the bot to wait.
what it looks like
invented example: harriet turns a monthly intake sheet into a table.
before
a report title sits above a3:e18. notes begin below row 18. selecting everything would mix three different things.after the bot
the bot proposes a3:e18, with headers. harriet approves that range. the table holds the intake records; the title and notes stay outside.an illustration with made-up names and numbers.
try it in 2 minutes
- connect excel with read and write
- name a workbook, sheet and a small range
- ask for a range preview, with no changes
- open excel and confirm the selected top row contains column names
before making the table
- the workbook and sheet are right
- the range starts at the column names
- notes sit outside the selected cells
- no table already occupies that range
mistakes people make
selecting the whole report
choose the data and its column names. leave titles and footnotes outside.
expecting an approval card for a table
require a preview and your go-ahead in the request. table creation does not use the send setting.
questions
do i need to type the data again?
no, keep the existing cells. this action creates a table around them. it takes no new row values.
what if the report title sits above my column names?
start at the column names. say that row contains headers and check the range before creation.
sources
read next
an excel bot for the workbook you actually meanconnected workbooks or a file in chat.
a file organizer bot that lists its moves firstone folder, a backup, a plan first.
find the excel workbook before reading its cellsfind candidate workbooks before opening.
claude connectors: connect the job you actually needpick a task before you connect an app.
an airtable assistant that learns the table before writingread the fields before filling the rows.
an asana assistant for the work between tasksfind the work holding up the handoff.
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].