> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/external-apps-integration/microsoft-teams.md). # Microsoft Teams Microsoft Teams integration in Lleverage lets your workflows react to what happens in your Teams channels. Connect a Teams account and start workflows automatically whenever a new message is posted in a channel you choose. ### Key Features * **New channel message trigger** - Start a workflow the moment a message is posted in a specific team channel * **Instant reaction** - Teams notifies Lleverage when a message arrives, so workflows start straight away rather than waiting for a scheduled check * **Message details** - The trigger provides the message content and sender details for use in the rest of your workflow * **Secure connection** - Teams is a native Lleverage integration, connected with your Microsoft account > 💡 The Teams integration currently provides a trigger rather than actions: it starts workflows when something happens in Teams. To send messages or manage channels as workflow steps, combine it with other integrations such as Outlook or Slack, or request the Teams actions you need via support. ### How to Use the New Channel Message Trigger 1. **Add the trigger** to your workflow and choose Microsoft Teams 2. **Choose a connection**, or connect a Microsoft account if you haven't yet 3. **Select the team** you want to listen to 4. **Select the channel** within that team 5. **Save and publish** - the workflow now starts every time a new message is posted in that channel > 💡 **Use case**: Triage support requests posted in a shared channel, log important announcements, or kick off follow-up processes whenever a team posts an update. ### Important Considerations * The connected account needs access to the team and channel you want to listen to * Each trigger listens to one specific channel; add more triggers for more channels * Message content becomes available as variables for the rest of the workflow > ⚠️ **Frequency**: Busy channels can start the workflow often. Keep an eye on your plan's workflow runs when listening to high-traffic channels. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/external-apps-integration/microsoft-teams.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.