Productivity · Integration
Microsoft Lists
Add Microsoft Lists to your product for your customers, and give your AI agents governed access to it.
Embed a Microsoft Lists integration so your product can work the lists your customers already use to track requests, inventory, issues and approvals. Lists are user-built, so every one has its own columns, choice values and views, and mapping them is configuration per customer rather than code on your side. fastn handles per-tenant OAuth, token refresh, paging over large lists and API upkeep, and delivers item changes as events so your product reacts when someone edits a row.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own tenant so your product reads and writes items in the lists they choose.
Create items from your product so a request captured in your app appears in the list a team already watches.
Read a list's columns and choice values so your product offers each customer's real fields rather than a fixed schema.
Trigger your product when a list item is created or its status column changes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a list and reports which items are unassigned or overdue.
An agent creates or updates an item within governed permissions, with the write logged.
An agent reacts to an item change and continues the workflow it belongs to.
Example prompt
Show open items in this request list with no owner and assign them by the routing rules we use.
Set up Microsoft Lists in 4 steps
- 01Open the Microsoft Lists connector from your fastn dashboard.
- 02Have each customer authenticate their own Microsoft 365 account with the scopes your product needs.
- 03Map the lists, columns and views 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 Lists integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Microsoft Lists integration without building it. Your customers connect their own Microsoft Lists account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Microsoft Lists update is not your on-call problem.
- One integration serves your product and your agents. The same governed Microsoft Lists connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Microsoft PlannerWorks well with
AirtableOften used alongside
Tools the same teams tend to run next to Microsoft Lists, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceMicrosoft Lists integration FAQ
How do I add a Microsoft Lists integration to my product?
Enable the Microsoft Lists connector in your fastn dashboard, then let each customer authenticate their own Microsoft Lists account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Microsoft Lists 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 Lists account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Microsoft Lists account and only ever sees their own work items, assignees and due dates. 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 Lists 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 list and reports which items are unassigned or overdue.
Who maintains the Microsoft Lists integration?
fastn does. When Microsoft Lists 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.
Can my product create and update work in Microsoft Lists automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Microsoft Lists can trigger your workflows in return.
Does it adapt to each team's own Microsoft Lists setup?
Yes. However a team has configured Microsoft Lists, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Microsoft Lists integration?
A common starting point: connect their own tenant so your product reads and writes items in the lists they choose. 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 Lists integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Microsoft Lists does not change your per-connector cost. You can start free with 3 connected accounts.
Add Microsoft Lists to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.