> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/reference/working-with-actions/slack-message-action.md).
# Slack Message
UI Bakery allows you to send Slack messages from your action to a predefined channel webhook.
By default, you can send plain text messages like this:
```javascript
{
text: 'Hello World!'
}
```
Slack API returns the `"ok"` string if the message was sent successfully.
In addition to sending text messages, you can also reference the data from the previous step or the data of the UI component:
```javascript
{
text: 'Hello ' + {{data.name}} + '!'
}
```
```javascript
{
text: 'Hello ' + {{ui.input.value}} + '!',
}
```
***
You can also use Slack's [extended message formatting options](https://api.slack.com/messaging/webhooks#advanced_message_formatting), such as block & attachments.
---
# 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.uibakery.io/reference/working-with-actions/slack-message-action.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.
