> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/faq/plugins/collaborative-tools.md).
# Collaborative tools
***
### How do I add a webhook?
A procedure is [available here](/doc-plugins/plugin-glpi-network/collaborative-tools.md) to help you.
***
### What is a Webhook?
A webhook can send notifications to an instant messenger. You can then follow the arrival of tickets via this channel.
***
### Which messaging services are supported?
The messsageries supported are :
* 
**Mattermost**,
* 
**Microsoft Teams**,
* 
**Rocket.Chat**,
* 
**Slack**,
* 
**Telegram**.
***
### Why am I not receiving the notification in the desired channel?
This may be due to several factors:
* Check that your application is correctly configured on the provider side
* Check in the recipient tab of each notification (new ticket, new follow-up, etc.) that your webhook is present.
* Check that there are no items in your queue
***
### Can I customise webhook notifications?
Yes, in **`setup`** > **`notifications`** > **`notification templates`**. Click on add and create your template. Then in **`setup`** > **`notifications`** > **`notifications`**, choose which notification you want to associate your new template with. In the template tab, click on **`add a template`** and select the template you created earlier.
***
### Why am I getting an error message with Power Automate/Teams?
When copying the URL from Microsoft, port `:443` is often included. We recommend removing this port and testing your webhook again.
---
# 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://help.glpi-project.org/faq/plugins/collaborative-tools.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.