Data & Storage · Integration
Microsoft Excel
Add Microsoft Excel to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Excel integration so your customers can read and write their own workbooks, worksheets, tables, and cell ranges from inside your product. Every workbook is laid out differently, so sheet and column mapping is configuration per customer rather than code, and access runs through each customer's own grant so their existing file permissions apply. fastn handles per-customer authorisation, token refresh, and API upkeep, so onboarding another tenant is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers pull rows from their own Excel workbooks into your product, mapped to their columns.
Write results back into a worksheet or table so users get output in the file they already work in.
Read a table's headers at runtime so your product adapts to each customer's own layout.
Refresh reads on a schedule so figures in your product follow the workbook instead of a one-off upload.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a range or table before answering a question grounded in the customer's own numbers.
An agent appends or updates rows within governed permissions, with each write logged.
An agent reads a workbook on a schedule and reports what changed since the last run.
Example prompt
Read the pipeline table in this workbook and list the rows with a close date in the past and no status set.
Set up Microsoft Excel in 4 steps
- 01Open the Microsoft Excel connector from your fastn dashboard.
- 02Have each customer authenticate their own Microsoft account and select workbooks.
- 03Map the worksheets, tables, and columns your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Microsoft Excel integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Excel integration without building it. Your customers connect their own Microsoft Excel account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Excel update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Excel connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Airtable
Power BIWorks well with
Google DocsOften used alongside
Tools the same teams tend to run next to Microsoft Excel, across other categories.
Anthropic Claude
OpenAI
Hugging FaceMicrosoft Excel integration FAQ
How do I add a Microsoft Excel integration to my product?
Enable the Microsoft Excel connector in your fastn dashboard, then let each customer authenticate their own Microsoft Excel account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Excel client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Microsoft Excel account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Excel account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Microsoft Excel integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a range or table before answering a question grounded in the customer's own numbers.
Who maintains the Microsoft Excel integration?
fastn does. When Microsoft Excel changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Microsoft Excel integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Microsoft Excel reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Microsoft Excel integration?
A common starting point: pull rows from their own Excel workbooks into your product, mapped to their columns. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Microsoft Excel integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Excel does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Excel to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.