> For the complete documentation index, see [llms.txt](https://docs.dyrector.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dyrector.io/tutorials/create-chat-notifications.md).

# Create Chat Notifications

Chat notifications help you to get informed about your team's activity in an instant. As of now 3 platforms are supported:

* Discord,
* Slack,
* and Microsoft Teams.

You can get notifications about 4 events:

* new Node added,
* new Version created,
* successful and failed deployments,
* new teammate invited.

### Tutorial

Before you start creating your Notifications, make sure you have the webhook ready. You can find how to create a webhook for [**Discord**](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks), [**Slack**](https://api.slack.com/messaging/webhooks), and [**Microsoft Teams**](https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook) in their official documentations.

**Step 1:** Click 'Notifications' on the left side.

**Step 2:** Select one of the 3 supported chat platforms.

<figure><img src="https://315393028-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCNvxW8k55ZlpJfMk8Oep%2Fuploads%2F5cdM2hNKiC0ymv7uyvWX%2Fdyrector-io-notifications.png?alt=media&amp;token=5ada67d4-0d34-4a0c-a5a1-f2f320de8fe4" alt=""><figcaption></figcaption></figure>

**Step 3:** Enter the following data:

* name of your notification,
* webhook URL.

**Step 4:** Set the toggle for 'Active' or 'Inactive' notifications. You can change this later to activate or inactivate the notifications.

**Step 5:** Click 'Save' on the top right.

{% hint style="info" %}
To test your notification, head to Notifications on the left, select the Notification you'd like to test and press the Test webhook message button.
{% endhint %}


---

# 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://docs.dyrector.io/tutorials/create-chat-notifications.md?ask=<question>&goal=<user_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.