Microsoft Excel

Form submissions, ecommerce orders, and CMS content all live in your site's data, and none of it lands in a spreadsheet on its own. Teams that track leads or reconcile orders in Microsoft Excel export files by hand after every change. The reverse is just as common: content already sits in a workbook, and someone retypes it into the Webflow CMS.

Excel is not a Webflow integration in the usual sense. No app in the Marketplace connects the two, nothing inside Webflow opens a workbook, and the CMS importer will not accept an .xlsx file. What does exist is a set of practical routes: a read-only embed of a live workbook on a page, a CSV import into a Collection, an automation platform sitting between the two products, and custom code against the Webflow Data API and Microsoft Graph. This page covers each route and what it costs you.

How to integrate Microsoft Excel with Webflow

What is Microsoft Excel? Microsoft Excel is the spreadsheet application in Microsoft 365. It runs on Windows and macOS, on iOS and Android, and in a browser as Excel for the web. Workbooks stored in OneDrive or SharePoint can be read and written programmatically through Microsoft Graph, which is what makes any automated connection to a Webflow site possible.

The practical question is how workbook data reaches a Webflow site and how site data flows back into the workbook. Sales teams want every form lead in a shared tracker without copy-paste, and finance wants order data in the workbook behind their PivotTable dashboards. An agency has a different reason again: letting a client update a price list by editing rows instead of logging into the CMS.

Three approaches connect the two platforms, ordered from least to most technical:

• Embeds and CSV import put a live workbook on a page or move spreadsheet rows into the CMS, with no automation tooling involved.
• Automation platforms such as Zapier, n8n, and viaSocket sync form submissions, orders, and CMS items with Excel tables on a hosted schedule.
• The Webflow and Microsoft Graph APIs give you full control over reads and writes in both directions, and require server-side development.

Most builds combine two of them, usually a CSV import to seed a Collection and an automation running behind it afterwards.

One thing to check before building any of it: Microsoft ships official MCP servers, and none of them covers Excel. Microsoft's MCP catalog lists servers for Word, for OneDrive and SharePoint, and for Teams, so an agent can reach the file without reading the cells inside it. The Webflow half is better served. Our MCP server lets a connected AI client create Collections, define fields, bulk-update items, and publish them, which covers most of what a spreadsheet-to-CMS script would otherwise do. Paste a block of rows into the client and it can build the Collection and fill it, with no code and no automation seat.

Embed Excel workbooks and import CSVs to the CMS

These two routes need no automation tooling and no code beyond pasting an iframe. A Code Embed element puts a read-only but interactive view of a live workbook on a page, while a CSV import moves spreadsheet rows into a Collection in bulk. The import route suits one-time migrations and content prepared in Excel before launch.

Where the workbook lives decides which embed path you get. A file in personal OneDrive generates its own iframe code. A file in SharePoint or OneDrive for Business embeds through URL parameters instead, which is also how you turn on filtering, PivotTable interaction, and BI views. CSV import ignores storage entirely and turns rows into CMS items you can style like any other Collection content.

Embed a workbook from OneDrive with Code Embed

Workbooks stored in personal OneDrive generate iframe code that pastes straight into a Code Embed element. Visitors can sort, filter, and calculate in the embedded view without signing in, and changes you save in OneDrive appear in the embed on their own.

To embed the workbook:

1. In OneDrive, right-click the workbook, select Embed, then Generate, and copy the iframe code.
2. In Webflow, add a Code Embed element from the Add panel and paste the iframe code.
3. Click Save and close, then publish the site.

Code Embed needs a paid Site plan or a paid Workspace plan. Visitors cannot edit the workbook from the embedded view; the embed is read-only by design, so treat it as a published report rather than a shared editing surface.

Embed from SharePoint or OneDrive for Business

Business workbooks embed through URL parameters rather than generated iframe code. This path fits teams whose files already live in SharePoint Online or OneDrive for Business, and it accepts BI parameters such as wdbipreview=True.

To build the embed URL:

1. Copy the workbook's URL from SharePoint or OneDrive for Business.
2. Append action=embedview to present the workbook as embedded.
3. Add wdAllowInteractivity=True to allow filtering and PivotTable interaction, and wdbipreview=True for Power View and Data Model-based slicers.
4. Place the resulting URL in an iframe src.
5. Paste the iframe into a Code Embed element, then publish the site.

Anonymous viewing depends on how the file is shared: give Everyone "Can view" permission and leave "Require Sign-in" unchecked. A SharePoint administrator can override that by defaulting Require Sign-in to True, and visitors then hit a login wall instead of your table. Microsoft documents the full parameter list in its SharePoint and OneDrive for Business embed guide, linked beside this article.

Import Excel data into the Webflow CMS

The CMS importer takes CSV, not .xlsx, so a workbook always goes through a Save As step first. That conversion costs you whatever a CSV cannot carry: formulas arrive as their computed values, formatting disappears, and only one worksheet crosses over per file. The CMS import guide walks through the field mapping step.

To import the data:

1. In Excel, arrange columns as Collection fields and rows as items, then save with the "Comma Separated Values" export type. Other CSV variants can render incorrectly on import.
2. In your Collection, choose Import and upload the CSV.
3. Map each column to a Collection field and confirm the import.

Upload file-field assets manually afterwards, since a CSV column cannot map to a file field. You can update existing items instead of creating new ones by including their Item IDs in a column, and multi-reference values separate with semicolons, such as "Charles Dickens; Jane Austen".

Connect with Zapier, n8n, or viaSocket

An automation platform is the middle ground: no server to run, and both directions covered. Zapier carries the most pre-built templates for this pairing, spanning form submissions, orders, and CMS items each way. Its Excel connector reads files stored on OneDrive for Business only, so local workbooks and personal OneDrive files are out.

Four pairings cover most of what teams actually build:

• Form submission to new row: Webflow's New Form Submission trigger with Excel's Add Row to Table action logs each lead the moment the form fires.
• Orders to an order tracker: New Order or Updated Order feeds Add Row to Table or Update Row, which keeps a reconciliation sheet current.
• Spreadsheet row to live CMS item: Excel's New Row in Table trigger with Webflow's Create Live Item action publishes a CMS item straight from the sheet.
• Updated row to updated item: Excel's Updated Row trigger with Webflow's Update Live Item action keeps published content matched to the workbook.

Start from the ready-made Webflow and Excel templates rather than wiring any of these by hand.

n8n is the self-hosted option for the same pairing. Its Webflow node handles create, delete, get, get many, and update operations, and its Webflow triggers cover Collection Item Created, Form Submission, Ecomm New Order, and Site Publish. The Microsoft Excel 365 node adds rows to the end of a table, appends data to a sheet, and updates rows in a sheet or range, as listed on the n8n Excel integration page. viaSocket runs the Webflow-to-Excel direction only, with New Form Submission and Collection Item Created triggers feeding Add Row To Table and Update Row actions, and no Excel-side trigger at all.

Two constraints apply on the Excel side whichever platform you pick. Row operations work against named Excel tables rather than loose ranges, so a flow pointed at a bare worksheet fails until you format the destination as a table. And nothing on the Excel side is genuinely event-driven, so a trigger watching for new or changed rows polls on a schedule set by your plan instead of firing when someone types.

Build with the Webflow and Microsoft Graph APIs

Custom code is the only path that gives you control over timing, field mapping, and publish behavior, and it costs you a server. The Excel endpoints in Microsoft Graph work on Office Open XML workbooks stored in OneDrive for Business or SharePoint. Workbooks on consumer OneDrive are not supported, and neither are .xls files. Authentication uses OAuth 2.0, with the Files.ReadWrite scope for anything that writes.

On the Webflow side, the Webflow Data API moves the content. Its List Collection Items endpoint reads CMS items and its List Form Submissions endpoint reads leads, while webhooks push events such as form_submission, collection_item_created, and ecomm_new_order to your endpoint as they happen.

None of this belongs in the browser. Graph file responses are not usable from front-end JavaScript, and a Webflow API token has no business sitting in client-side code, so a small server or a serverless function is the practical architecture.

Send Webflow form submissions to an Excel table

This direction is fully event-driven. The webhook posts a JSON payload to your endpoint the moment a form fires, and your server writes that payload into a workbook table through Graph.

To implement this:

1. Register a webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks using the form_submission trigger type. An optional filter object targets a single form, per the webhook creation reference.
2. Verify each delivery by computing a SHA-256 HMAC of timestamp + ":" + JSON.stringify(body) with your OAuth application's client secret, or your secret key when the webhook is not tied to an OAuth app. Reject requests whose timestamp is more than 5 minutes old.
3. Create a workbook session with POST /me/drive/items/{id}/workbook/createSession and pass the returned ID as the workbook-session-id header on later calls.
4. Append the submission with POST /me/drive/items/{id}/workbook/tables/{id|name}/rows/add and the body { "values": [["field1", "field2", "field3"]] }. Batch several rows per call where you can.
5. Close the session with POST /me/drive/items/{id}/workbook/closeSession.

Microsoft notes that a persistent session typically expires after about 5 minutes of inactivity and returns a 404 once it has. Graph also exposes a refresh call, so a long-running process can either keep a session alive or open a fresh one per batch.

Sync Excel rows to Webflow CMS items

This direction reads workbook data through Graph and writes it to Collections through the Data API. It fits catalogs, directories, and price lists that a team maintains in a spreadsheet.

To implement this:

1. Read rows with GET /me/drive/items/{id}/workbook/tables/{id|name}/rows, or pull the whole sheet with GET /me/drive/items/{id}/workbook/worksheets/{id|name}/usedRange(valuesOnly=true).
2. Create items in bulk with POST https://api.webflow.com/v2/collections/{collection_id}/items/bulk, which accepts up to 100 items per request. Each item's fieldData needs name and slug, per the bulk create reference.
3. Publish staged items with POST /v2/collections/{collection_id}/items/publish, or write straight to POST /v2/collections/{collection_id}/items/live to skip the staging step.

Graph change notifications do not cover workbook, worksheet, table, or range resources, so nothing tells you a cell changed. Detect edits by polling on a schedule, or subscribe to file-level driveItem changes, which fire on save.

What you can build with the Microsoft Excel Webflow integration

Pairing Excel with Webflow lets you run spreadsheet-driven content and reporting without manual exports or retyping data between systems. The four builds below cover the cases teams reach for most.

• Lead tracking workbooks: Route every form submission into a shared tracker so a sales team works from a live lead log rather than a folder of exported CSVs.
• Spreadsheet-managed site content: Give a client a workbook where each row is a CMS item, updated live and rendered in a Collection List, so a property or directory listing never needs the CMS opened.
• Published pricing tables: Keep plan rows and feature comparisons in a workbook, embed it on the pricing page, and edit a row to change what visitors see without republishing the site.
• Ecommerce order reporting: Send new and updated orders into an Excel table and build PivotTable dashboards on top for revenue reconciliation.

Start with our CMS API guide if you need exact control over sync timing and field mapping. If you would rather not write the sync at all, connect the Webflow MCP server to your AI client first and let it build and fill the Collection from your rows.