> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.1/reference/step-definitions/send-message-to-teams.md).
# Send message to Teams
The **Send message to Teams** step leverages the WebHook Bot app to send messages from a task sequence to the specified Teams channel URL.
The URL is generated by the WebHook Bot when you integrate the app into a channel. The message can contain any text, with task sequence variable names (inclosed in percent signs) replaced by the current value of that variable.
See [ https://appsource.microsoft.com/en-us/product/office/WA200007770](< https://appsource.microsoft.com/en-us/product/office/WA200007770>) for more information on the needed configuration for this.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/deployr/1.1/reference/step-definitions/send-message-to-teams.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
