> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/collaboration/alerts/sending-slack-message.md).
# Sending Slack message
Sending Slack messages to your project channel or directly to people is the best way to keep your team updated on the status of test/suite/schedule runs.
{% hint style="warning" %}
Keep in mind that the "Alerts" feature is only available on paid plans.\
So any related features, such as Slack alerts, will not be available on the free plan.
More information about pricing can be found here:
{% endhint %}
Before proceeding to the first step, remember to [integrate your Slack workspace with BugBug](/integrations/slack.md#connect-your-slack-workspace-with-bugbug).\
If you haven't done so yet, don't worry - BugBug will prompt you for permissions when you start creating an alert.
Already connected? Great! Follow the steps below.
### Set Slack message type
In the first field, you need to specify the messaging method. We currently support two different ways to send a Slack message:
* Channel message *(most common)*
* Direct message
### Choose a recipient/channel
In the next box, you need to select a channel or person to receive the messages.\
BugBug will provide you with a list of all available Slack members.
### Testing a Slack alert
Before creating a new Slack alert, it's possible to check how it works by clicking on the **"Trigger Alert"** button.
{% hint style="info" %}
The Slack message template is predefined for all users.\
If you need to customize the message, [create a webhook alert instead](/collaboration/alerts/sending-webhook.md).
{% 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.bugbug.io/collaboration/alerts/sending-slack-message.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.
