# Slack MCP

## 1. Prerequisites

Before using the Slack MCP node you need:

* **A Slack account**: sign up at <https://slack.com/>
* **A Slack workspace**
* **An OAuth client app**: generated inside your Slack workspace. This gives you a **Client ID** and **Client Secret**.

***

## 2. Setting Up Slack Credentials

### 2.1 Create a new app in Slack

1. Go to [https://api.slack.com/apps/new](< https://api.slack.com/apps/new>)
2. Create a new app, either via manifest or from scratch.

<figure><img src="/files/rzeU0amQD3fc41PnSwOH" alt=""><figcaption></figcaption></figure>

3. After an app is created, grab the Client ID and Client Secret.

<figure><img src="/files/pDsz3h7JOIdaHk2aTn7P" alt=""><figcaption></figcaption></figure>

### 2.2 Add Credentials in Flowise

1. In Flowise, navigate to **Credentials** from the sidebar.
2. Click **Add Credential** and search for **Slack User Token OAuth2**.
3. Fill in the following fields:

<table><thead><tr><th>Field</th><th>Description</th><th width="250">Example</th></tr></thead><tbody><tr><td><strong>Client ID</strong></td><td>The OAuth Client ID from Slack</td><td><code>wBSGhxxxx</code></td></tr><tr><td><strong>Client Secret</strong></td><td>The OAuth Client Secret (stored securely)</td><td><code>••••••••</code></td></tr><tr><td><strong>Scopes</strong></td><td><em>(Optional)</em> Space-separated scopes.</td><td><p><code>search:read.public search:read.private search:read.mpim search:read.im search:read.files search:read.users groups:history</code></p><p><code>mpim:history</code></p><p><code>im:history</code></p><p><code>channels:history</code></p><p><code>chat:write</code></p><p><code>canvases:read canvases:write</code></p><p><code>users:read</code></p><p><code>users:read.email</code></p></td></tr></tbody></table>

4. Copy OAuth Redirect URL, then click **Save**.

<figure><img src="/files/DgHYVhNulWgZNyemxThk" alt="" width="548"><figcaption></figcaption></figure>

**Tip:** For production environments, use the narrowest scopes you need. See available [scopes](https://docs.slack.dev/reference/scopes/).

### 2.3 Add Redirect URL to Slack App

1. From the left side nav bar, select OAuth & Permissions:

<figure><img src="/files/wAxrxZEkEDuysN8lzvzt" alt=""><figcaption></figcaption></figure>

2. Scroll down and you will see Redirect URLs section. Add the copied redirect URL from previous step. Then click Save URLs.

<figure><img src="/files/bZlca7kkvD9mYYk2Tl3L" alt="" width="563"><figcaption></figcaption></figure>

***

## 3. Adding Slack MCP

1. Drag and drop an Agent node.
2. Add a new Slack MCP tool.

<figure><img src="/files/pYRDwSLzqBjldSA4oKbs" alt="" width="500"><figcaption></figcaption></figure>

3. Select preconfigured credential, and click the edit button. Click Authenticate.

<figure><img src="/files/8T3qRNMrF2KRuwcX8sy9" alt="" width="538"><figcaption></figcaption></figure>

3. A slack pop-up window will appear, review the permissions and click Allow.

<figure><img src="/files/n4HMmqeD83EZiNFnxb7z" alt="" width="542"><figcaption></figcaption></figure>

4. After authenticated, click the refresh button to load the available actions.

<figure><img src="/files/vEUVIDMIUrquOX4uV8Mr" alt=""><figcaption></figcaption></figure>

5. Select the actions. *Tip: Select only the actions your agent needs. Fewer tools help the LLM make better decisions and reduce token usage.*

<figure><img src="/files/M1IyWhaaPsPbcYNqxt9G" alt="" width="452"><figcaption></figcaption></figure>

6. Voila! You can start chatting with the Agent and see how its calling Slack MCP tools.

<figure><img src="/files/z8CJq6Yx3pcYRUvpxrgw" alt=""><figcaption></figcaption></figure>


---

# 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.flowiseai.com/integrations/langchain/tools/pipedream-mcp-user-guide-1.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.