Microsoft Teams, ready to run.
The Microsoft Teams integration is where the chase happens. Floowed asks for what is missing in the channel your team already uses, takes the answer or the file back into the case, and posts the outcome when it lands.
What it does.
What Floowed reads from Microsoft Teams
- Messages sent to the Floowed bot, or every channel message where the team granted ChannelMessage.Read.Group
- Files posted in a channel, from the team's SharePoint site over Microsoft Graph
- The answer from whoever owns the call, submitted on a card the bot posted
What it writes back
- The question, when a case is still missing something
- The decision and the reasoning, in the channel
- An approval card, before anything sensitive runs
Teams is a chase and approval surface rather than a source of truth. Posting runs through the app's bot: Microsoft Graph only lets an app post channel messages without a signed-in user for migrations. Approvals are cards the bot posts, not the Teams Approvals app, which can't be read app-only.
A supplier onboarding case, from request to vendor record.
- Gather
A request to add a supplier arrives in the procurement mailbox in Outlook. Floowed opens a case and collects the supplier's forms from the email.
- Interpret
It reads the tax form, bank letter and certificates, and checks them against the supplier's details and the contract filed in SharePoint.
- Chase
The insurance certificate is out of date and the budget owner hasn't confirmed the spend. Floowed replies to the supplier in the email thread and asks the budget owner in the procurement channel in Teams.
- Decide
Your onboarding rules run in a deterministic policy engine once everything is in. A supplier that doesn't fit the rules goes to the procurement lead, who answers on a card in Teams.
- Act
Floowed creates the vendor record in NetSuite, files the evidence in SharePoint, and posts the outcome in the Teams channel.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Microsoft Teams
Using a Teams app with a bot, registered in Microsoft Entra ID. 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 Teams?
Yes, as a Teams app with a bot, added to the teams you choose. Posting and replying run through the bot; channel files are read over Microsoft Graph.
How does the Microsoft Teams integration connect?
Your tenant allows the app, and a team owner adds it to a team and consents to its permissions for that team only. Channel files are read from the team's SharePoint site, which your admin can grant site by site.
What can Floowed do in Microsoft Teams?
It asks for what a case is missing, reads the reply or the file that comes back, posts an approval card before anything sensitive runs, and posts the outcome with its reasoning.
Does it use the Teams Approvals app?
No. Approvals are cards posted by the Floowed bot, and the answer goes straight back into the case.
Is my Microsoft Teams data secure?
Resource-specific consent is granted per team, not across the tenant, and removing the app from a team ends it. Consent is revocable in Microsoft Entra.
What does the Microsoft Teams 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 Teams. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.