--- title: "Microsoft Excel 365 Integration" description: "Read and write Excel 365 workbooks in OneDrive from your flows: append table rows, read ranges as objects, and manage worksheets and tables. Agents keep spreadsheets current and confirm before overwriting shared regions." url: https://flowrunner.ai/integrations/microsoft-excel date_modified: 2026-08-01T02:40:32-07:00 --- # Microsoft Excel 365 [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Read and write Excel 365 workbooks in OneDrive from your flows: append table rows, read ranges as objects, and manage worksheets and tables. Agents keep spreadsheets current and confirm before overwriting shared regions. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · OAuth · available [Microsoft Excel 365 website](https://microsoft.com/) · [Platform Documentation](https://learn.microsoft.com/en-us/graph/api/resources/excel) · Capability data verified 2026-08-12 1. A new record arrives from a form, email, or another service 2. Agent maps the record's fields to the table's columns 3. Agent confirms the record has the values the table needs 4. Agent selects the target workbook and table in OneDrive 5. Agent appends the record with Add Table Rows 6. Agent reads the used range to confirm the row landed 7. A record that would overwrite existing data is routed for a person to confirm ## What This Integration Enables FlowRunner agents use Excel 365 to keep spreadsheets current as decisions, not manual entry. An agent can append form submissions, leads, or orders as rows to an Excel table, read a range as objects and feed each row into downstream steps, and write computed values into a report range. It can provision worksheets and tables on demand, and clear and rebuild a data region on a schedule. Because writes accept arrays of objects keyed by header, the agent maps fields by name rather than by fragile cell position. The routine appends and reads run on their own. The overwrite of a range or the clearing of a region others depend on is where the agent stops to ask. ### Without FlowRunner **Manual data entry**: Records are typed into the spreadsheet by hand as they arrive **Broken formulas**: A misaligned paste shifts columns and breaks the sheet's formulas **Stale reports**: The shared report is only as current as the last person who updated it ### With FlowRunner **Rows append themselves**: Records are added to the Excel table automatically, keyed by column name **Clean writes**: Object-keyed writes map to the right columns, so formulas keep working **Current reports**: The sheet updates as records arrive, so the report reflects reality ## Use Case Scenarios ### Form Submissions to a Tracking Table Form submissions arrive. The agent maps each to the Excel table's columns and appends it with Add Table Rows, keyed by column name so every field lands in the right place. Batching multiple rows in one call keeps the write fast. The tracking sheet stays current without anyone retyping data. ### Range Read to Downstream Steps The agent reads a data region with Get Range Values and First Row As Headers enabled, so each row comes back as an object keyed by the header. It feeds those objects into downstream workflow steps, then emails a formatted summary. Because the read returns real fields, the flow works with names, not cell coordinates. ### Nightly Rebuild with an Overwrite Gate On a schedule, the agent refreshes a computed region by clearing it with Clear Range and writing fresh values with Update Range Values. When the region is a shared report others edit, the agent does not clear and overwrite blindly. It flags the report owner to confirm before the previous values are replaced. ## Human-in-Loop Highlight When an agent is about to run Update Range Values or Clear Range over a shared report region, it does not just overwrite it. Replacing a range others edit can wipe manual annotations and break downstream views, and the previous values are gone. The agent pauses and routes to the report owner through their preferred channel: "Ready to rebuild \[Range\] on \[Workbook\]. This replaces the current values, including any manual edits. Overwrite now or review first?" The owner decides, and the agent runs the write only on confirmation. Routine appends and reads run on their own; overwriting shared work reaches a person first. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Workbooks 1 - **List Workbooks** Searches the connected user's OneDrive for Excel workbooks and returns each workbook's ID, name, and path. Used to resolve which workbook to operate on. Workbooks are created in OneDrive first, then selected here. ### Worksheets 3 - **List Worksheets** Retrieves the worksheets in a workbook with their IDs, names, and positions. Used to resolve which sheet to read or write. - **Add Worksheet** Adds a worksheet at the end of the workbook. Used to provision a sheet for a project or period. - **Delete Worksheet** Deletes a worksheet and its data. A workbook must keep at least one sheet. Used in cleanup. ### Ranges 4 - **Get Range Values** Reads a worksheet range as a two-dimensional array, and as objects keyed by headers when First Row As Headers is enabled. Used to feed rows into downstream steps. - **Update Range Values** Writes values to a range, accepting a two-dimensional array or an array of objects. Used to write computed values, gated behind a human confirmation on shared reports. - **Get Used Range** Retrieves the smallest range containing all data on a worksheet, with values and optional header objects. Used to read a whole data region without knowing its bounds. - **Clear Range** Clears a range's values, formatting, or both, without deleting the cells. Used to reset a region before a rebuild, gated on shared reports. ### Tables 6 - **List Tables** Retrieves the Excel tables in a workbook with their settings. Used to resolve which table to append to. - **Create Table** Creates an Excel table over a worksheet range, optionally using the first row as headers. Used to provision a structured table on demand. - **Add Table Rows** Appends one or more rows to an Excel table, mapping object keys to columns automatically. Used to log records as they arrive, faster in a batch than one at a time. - **List Table Rows** Retrieves an Excel table's data rows as objects keyed by column name. Used to read the table's contents for processing. - **List Table Columns** Retrieves an Excel table's columns with their names, indexes, and values. Used to map incoming fields to the right columns. - **Delete Table Row** Deletes a single data row from an Excel table by its zero-based index. Used in cleanup. ## Frequently Asked Questions ### What can FlowRunner do with Microsoft Excel 365? FlowRunner agents can run List Workbooks, List Worksheets, and Add Worksheet in Microsoft Excel 365, plus 11 more actions. ### Does connecting Microsoft Excel 365 to FlowRunner require OAuth? Yes. Microsoft Excel 365 connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Microsoft Excel 365 trigger a FlowRunner workflow automatically? Microsoft Excel 365 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Microsoft Excel 365?** This integration exposes Microsoft Excel 365 to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/microsoft-excel. Site index: https://flowrunner.ai/llms.txt