Overview
Stay on top of every deal without leaving Teams. The Flowla × Microsoft Teams integration allows your team to stay on top of deal activity without leaving Teams. Once connected, Flowla can send automated notifications to any Teams channel or directly to individual users whenever key events happen in your rooms — like a prospect downloading an asset, viewing a room, or leaving a comment.Channel notifications
Route alerts to shared channels so your whole team sees deal activity as it happens.
Direct messages
Send notifications privately to individual team members.
Room owner alerts
Flowla detects who owns a room and notifies them automatically.
Granular control
Choose which events trigger notifications and configure separate rules per recipient.
Requirements
Before setting up the integration, make sure you have:- A Microsoft 365 account with permission to grant admin consent for your organization (typically a Teams or Azure AD administrator)
- The Flowla Teams bot installed in at least one Teams team (required for sending notifications to channels and DMs — see Installation below)
- Admin access in Flowla to manage integrations
Setting Up the Integration
The setup has two parts:
Both steps are required. You can send notifications to channels or DMs only after the bot has been installed in a team.
Part 1 — Connect Your Microsoft Tenant
Open the integration settings
In the left sidebar, click Integrations, then select Microsoft Teams and click Connect.
Sign in to Microsoft
You will be redirected to a Microsoft login page. Sign in with your Microsoft 365 account and review the permissions Flowla is requesting.
Grant consent
This authorization grants Flowla permission to read your Teams structure (teams, channels, members) and send messages via the Flowla bot. It does not give Flowla access to your Teams messages or files.
Part 2 — Install the Flowla Bot
The Flowla bot must be installed in at least one Microsoft Teams team before notifications can be sent. Choose the option that fits your use case:- Channel notifications
- Direct messages (DMs)
To send notifications to a Teams channel, install the Flowla bot directly into the team that contains the channel.
Once installed, Flowla can post to any channel in that team. You will see a welcome message from the Flowla bot in the General channel confirming the installation.
Only standard (public) channels are supported. Private channels are not available.
Available Notifications
You can configure Flowla to notify you whenever any of the following events occur in your rooms:| Notification | Description |
|---|---|
| Asset Downloaded | A visitor downloaded a file or asset from a room |
| Comment Added | A visitor or team member added a comment in a room |
| Room Viewed | A visitor opened and viewed a room |
| Room Shared | A room was shared with a new recipient |
| Reaction Added | A visitor or team member commented in the room with an emoji or reaction in mobile view |
| Task Completed | A task inside a room was marked as complete |
| Overdue Reminder | A task or action item in a room is past its due date |
Managing Notification Settings
Notification rules (called Notification Sets) define who receives which notifications. Each rule targets a single recipient — a channel, a specific user, or the room’s owner — and specifies which events to deliver.Accessing Notification Settings
- In the left sidebar, click Integrations, then select Microsoft Teams
- Your configured notification sets are listed in the left panel
- Click any existing rule to edit it, or click Add to create a new one
Creating a Notification Rule
Select a Recipient Type
- Channel — sends the notification to a Teams channel
- User — sends the notification as a direct message to a specific team member
- Room Owner — automatically sends the notification to whoever owns the Flowla room the event occurred in
Select the Recipient
- If Channel: choose from the list of available channels in the selected team
- If User: search for and select a team member by name
- If Room Owner: no additional selection needed — Flowla resolves the owner automatically
Editing a Notification Rule
- Click the rule you want to edit from the left panel
- Modify the recipient, notification types, or active status
- Click Save to apply changes
Deleting a Notification Rule
- Select the rule from the left panel
- Click Delete at the bottom of the editor
- Confirm deletion — this cannot be undone
Disconnecting Microsoft Teams
Disconnecting from Flowla does not uninstall the Flowla bot from your Teams workspace. To fully remove the bot, go to Microsoft Teams → manage the team → Apps → remove the Flowla app.
Troubleshooting
I connected my tenant but no notifications are being delivered
I connected my tenant but no notifications are being delivered
Likely cause: The Flowla bot has not been installed in a Teams team. The OAuth connection alone is not sufficient for message delivery.Fix: Install the Flowla bot in at least one Microsoft Teams team — see Part 2 of the setup instructions above.
I can't find a channel in the dropdown
I can't find a channel in the dropdown
Likely cause: Private channels are not supported by the integration.Fix: Only standard (public) channels are shown. Check that the channel you’re looking for is not set to private in Teams.
A team member is not receiving DMs
A team member is not receiving DMs
Likely cause: The Flowla bot has not been installed in a team that the user is a member of.Fix: Ensure the bot installation (Part 2) has been completed for a team that includes this user, or have the user install the Flowla app in their personal Teams space.
The room owner notification isn't being delivered
The room owner notification isn't being delivered
Likely cause: The room owner’s email in Flowla does not match their email in the connected Microsoft Teams tenant.Fix: Verify that the room owner’s Flowla email matches their Microsoft 365 account email exactly.
I get an error when trying to connect
I get an error when trying to connect
Likely cause: The account used does not have Microsoft 365 admin permissions to grant consent on behalf of the organization.Fix: Sign in with an account that has admin rights. Personal or standard user accounts cannot authorize the integration.