# Slack

## Events API

Some components (NewChannelMessageRT) use Slack Events API (<https://api.slack.com/events-api>). In order to use this component(s) in Appmixer you have to register Appmixer's Slack URI in Slack first.

Go to <https://api.slack.com/apps> then choose your Appmixer app.

Go to your app settings ([https://api.slack.com/apps/{your-app-id}/event-subscriptions](https://api.slack.com/apps/A2WEBMFC6/event-subscriptions?))

![Slack Even Subscription.](/files/-MOCZhVFTo4p4kJXPsYc)

The *Request URL* has to point to your Appmixer backend server. The rest of the URL /services/appmixer/slack/events has to remain like this. Your Appmixer backend server has to be running before you enter the URL. Slack will immediately try to connect to that URL.

Then you need to subscribe to `messages.channels` and `message.groups` events.

![](/files/-MOCbBvisVst0IVSsm9n)

Don't forget to hit *Save Changes:*

![](/files/-MOCba4N82pJmUj-MLvE)

You can now use the appmixer.slack.list.NewChannelMessageRT component in a flow.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.appmixer.com/6.0/v4.1/app-registration/slack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
