Microsoft 365, ready to run.
Most operational decisions already live somewhere in Microsoft 365. The case arrives as email, the evidence is in SharePoint, the chasing happens in Teams, and the reference data is in a spreadsheet. Floowed reads across them and applies your rules.
What it does.
What Floowed reads from Microsoft 365
- Mail and attachments, from the mailboxes your admin grants
- Documents in the SharePoint and OneDrive libraries you grant
- Messages and files in the Teams channels the app is added to
- Workbooks, where a signed-in user connects them
What it writes back
- The chase, as a reply in the thread or a message in the channel
- The decision and its reasoning, filed where the evidence sits
- An approval card in Teams, before anything sensitive runs
Microsoft 365 is not one integration, so each part is granted on its own. Mail is granted in Exchange Online with RBAC for Applications, scoped to named mailboxes. Files are granted site by site with Sites.Selected. Teams is consented per team, and posting runs through the app's bot. Excel is the exception: Microsoft's workbook API does not support application permissions, so it needs a signed-in user.
A contract renewal case, from the notice email to the signed renewal.
- Gather
A customer's renewal notice lands in the contracts mailbox. Floowed opens the case, pulls the current contract from SharePoint and the account from Salesforce.
- Interpret
It reads the contract's renewal and pricing terms and compares them with the usage and invoices in NetSuite.
- Chase
The account owner hasn't confirmed the new scope. Floowed asks in the account team's Teams channel and replies to the customer in the email thread for their updated purchase order.
- Decide
Your renewal rules run in a deterministic policy engine. A discount above what the rules allow goes to the commercial lead to approve on a card in Teams.
- Act
Floowed sends the renewal for signature in DocuSign, files the signed copy in SharePoint, updates the subscription in NetSuite and the opportunity in Salesforce.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Microsoft 365
Using Microsoft Graph, scoped by your admin. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
More in Communication.
Questions
Does Floowed integrate with Microsoft 365?
Yes, through Microsoft Graph, across Outlook mail, SharePoint, OneDrive, Teams and Excel. Each part is granted and scoped separately.
How does the Microsoft 365 integration connect?
Your admin grants each part at the narrowest level Microsoft offers: named mailboxes through RBAC for Applications, named sites through Sites.Selected, and named teams through resource-specific consent.
What can Floowed do across Microsoft 365?
Run one case across the parts. An email arrives with an attachment, the contract is in SharePoint, the question goes to Teams, and the decision and its reasoning land back where your team already looks.
Does all of it run unattended?
Mail, SharePoint, OneDrive and Teams do, once granted. Excel does not: Microsoft's workbook API has no application permission and needs a signed-in user.
Is my Microsoft 365 data secure?
Every part is scoped by your admin and revocable. Make sure no wider grant is left beside a scoped one: for mail, a tenant-wide Mail permission consented in Microsoft Entra adds to the scoped Exchange grant, so leaving it in place undoes the scoping.
What does the Microsoft 365 integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.
Start with Microsoft 365. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.