Post notifications and capture activity from Microsoft Teams.
Microsoft Teams
Post notifications and capture activity from Microsoft Teams.
Flows360 gives operators an end-to-end view of Microsoft Teams alongside the rest of their stack — sync the objects that matter, run the actions you need, and trigger workflows on real-time events without writing glue code.
Common use cases
- Route alerts from any Flows360 workflow to a Teams channel
- Trigger workflows when a Teams message matches a keyword
- Notify on-call rotations via channel mentions
Sync scenarios
- Post deal-stage changes from your CRM into a Teams channel
- Open a Teams chat when a high-priority ticket arrives
- Mirror Teams meeting outcomes back into the CRM
Objects supported
- Message
- Channel
- User
Actions
- send_message
- list_channels
- message_received
Frequently asked questions
Does this work with Teams free?
It works with any Teams tenant that supports Graph API app permissions.
Can I scope to a single channel?
Yes, channel and team IDs are selectable per workflow step.
- Auth method: OAuth 2.0
- Required scopes: 2
- Supported objects: 3
- Supported actions: 4
Overview
The Flows360 connector for Microsoft Teams lets you build reliable, bidirectional integrations between Microsoft Teams and the other tools your teams rely on every day. Move records, trigger downstream workflows, and keep data consistent across CRMs, ERPs, data warehouses, support desks, and internal apps — without writing or maintaining glue code.
Use this connector to eliminate manual data entry, reduce swivel-chair work between systems, and give every team a complete, real-time view of customers, operations, and pipeline. Flows360 handles authentication, pagination, retries, rate-limit backoff, and schema drift so your integrations stay healthy as Microsoft Teams evolves.
Setup steps
1. Sign in to Microsoft Teams
Log in to your Microsoft Teams account with an administrator user that can create or manage API credentials.
2. Create credentials for Flows360
In the Microsoft Teams admin area, create a new API key, service account, or OAuth application dedicated to Flows360. Grant it the minimum scopes required to read and write the objects you plan to sync.
3. Copy the credentials
Copy the generated client ID, client secret, API token, or service account key. Treat these values as secrets — they grant access to your Microsoft Teams data.
4. Connect from Flows360
In Flows360, open Connectors → Microsoft Teams → Connect. Paste the credentials into the matching fields and (for OAuth) complete the authorization redirect.
5. Test the connection
Run the built-in test in Flows360. A successful test confirms credentials, network access, and the required scopes. You can now use Microsoft Teams as a source or destination in any flow.
Required scopes
readwrite
Supported objects
- Record
- User
- Activity
Supported actions
- list_records — Retrieve records from Microsoft Teams with optional filters.
- create_record — Create a new record in Microsoft Teams.
- update_record — Update an existing record in Microsoft Teams by its ID.
- record_changed — Trigger a flow when a record in Microsoft Teams is created or updated.
Use cases
- Customer 360
- Marketing Automation
- Revenue Operations
- CRM to ERP Sync
Limitations
- Throughput is bounded by the Microsoft Teams API's published rate limits; Flows360 automatically retries with exponential backoff.
- Computed, derived, or read-only fields in Microsoft Teams cannot be written to from Flows360.
- Real-time triggers depend on Microsoft Teams supporting webhooks; otherwise Flows360 falls back to polling on the schedule you configure.
- Large historical backfills should be run during off-peak windows to avoid hitting daily API quotas.