List the Tabs of a Workbook
Lists every tab of the uploaded workbook in order, each with the heading text at the top of it.
Overview
An inspection workbook is not one form. It is a file of tabs, some of them a page of readings, the rest instructions, pick-lists, a field map, a worked example. Nothing in a tab's name says reliably which is which: two tabs called "App B" and "App B (2)" can be a real inspection and a sample.
This reads the top of every tab and hands the agent both the name and what is written there, which is what lets it say which tabs are pages and leave the rest alone.
What It Does
| Capability | What it means for you |
|---|---|
| Every tab, in workbook order | Nothing is filtered out before the agent sees it, so a tab it skips is a tab it decided to skip |
| The heading, not just the name | The first few texts at the top of each tab come back with it, which is where a form tab says which form it is |
| One read of the file | The workbook is read once and the tab names are the handles for everything that follows |
| Only a spreadsheet | An attachment that is not a workbook comes back refused rather than half read |
When the Agent Chooses This Tool
Available in the Coating QA workflow. The Fill Any Form, appraisal-report and pre-bid workflows do not have it.
The instructions call it once, on the workbook attached to the package, and pair it with the list of appendices the package can fill.
- A tab whose heading matches no appendix is left out, and the run says so rather than filling it.
- A tab of instructions, pick-lists, configuration, a field map or a worked example is never a page. The agent is told outright that an example tab looks exactly like a real one and that filling it would invent an inspection that never happened.
- When no tab reads as a form tab, the run stops and says so.
Inputs and Outputs
Takes: one attachment of this package.
Returns: every tab of the workbook in order, each as its name and the heading text read off the top of it.
Example
An inspector uploads the workbook for a vessel: eight tabs, five of them inspections, one of instructions, one pick-list, one worked example.
The agent lists the tabs, reads the headings, and matches five of them to the appendices the package can fill. The other three are named in the summary as left out, and no page is created for them.
Limits
- The heading is the top of the tab, not the whole of it. The first few texts of the first rows come back, long ones cut short, and nothing further down is read here.
- The tabs are reported, not judged. Which tab is a page is the agent's decision from the heading, and a workbook that labels a sample exactly like a real inspection can be read wrong.
- An attachment that is not a workbook is refused. A PDF or an image comes back as a refusal naming the file.
- A file the tool cannot open is refused with the reason, rather than reported as an empty workbook.
FAQ
Does the order of my tabs matter?
Yes. Tabs come back in workbook order, and the pages of the finished package follow the order the agent lists them in, so a workbook in the order you want to read it comes out that way.
What happens to my instructions and pick-list tabs?
They are listed like every other tab, and the agent is told to leave them out because their headings read as prose or as column labels rather than as a form title. The run names what it left out.
Can it read a Google Sheet or a CSV?
It reads the workbook you attach, and an attachment that is not a spreadsheet file is refused. A sheet exported to .xlsx is what it expects.