> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Slack is a channel-based messaging platform. Connect it to WPOS and the agent can use it as part of the work it does on your site.

Slack is where most teams already talk. Connected to WPOS, the agent can read and post messages, which is the usual way to get a site to tell your team something without anyone checking a dashboard.

**Category:** Messaging   **Actions available:** 158+

## What you can do

* Post messages to public and private channels
* Read channel history for context
* List channels, users, and conversations

## Example requests

Once Slack is connected, ask in the [Command Center](/operate/command-center):

```text theme={null}
Post to #general when this page goes live.
Send new form submissions to #leads.
Summarise what was decided in #website this week.
```

## Before you connect

* A Slack workspace you can install apps into. Owners and admins can install directly, members may need approval.
* Know which **channel** you want WPOS to post to, and whether it is public or private.
* If your workspace requires admin approval for new apps, request it before starting.

## Connect it

<Steps>
  <Step title="Open WPOS">
    In WordPress admin, open **WPOS**. You land on the chat screen.

    <Frame caption="WPOS opens on the chat screen.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/01-wpos-home.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=c6a37cef2115c9578ad03a8f96721a5a" alt="The WPOS chat screen in WordPress admin." width="1918" height="876" data-path="images/connectors/slack/01-wpos-home.png" />
    </Frame>
  </Step>

  <Step title="Open a new tab and choose Connectors">
    Click the **+** button to open the launcher panel, then choose **Connectors**.

    <Frame caption="The launcher panel. Connectors is the fifth entry.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/02-new-tab-connectors.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=6fcd99a5dd5f459675a17899ed7a13fb" alt="The WPOS launcher panel listing Preview, Site tree, Files, Skills, Connectors, and Settings." width="1920" height="887" data-path="images/connectors/slack/02-new-tab-connectors.png" />
    </Frame>
  </Step>

  <Step title="Find the connector">
    Every available connector is listed alphabetically, each with a button showing what it needs.

    <Frame caption="The Connectors panel, sorted alphabetically.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/03-connectors-list.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=49b5481933fbfdb42e19097fd741c097" alt="The WPOS Connectors panel listing Calendly, Canva, Figma, Google Analytics, Google Calendar, and Google Docs." width="1913" height="891" data-path="images/connectors/slack/03-connectors-list.png" />
    </Frame>
  </Step>

  <Step title="Search and press Connect">
    Type `Slack` into **Search for integrations**, then press **Connect**.

    <Frame caption="Search narrows the list to one row.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/04-search.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=024edb72e731a3e41b20f82c3a81f1a6" alt="The Slack row with a Connect button." width="1916" height="885" data-path="images/connectors/slack/04-search.png" />
    </Frame>
  </Step>

  <Step title="Sign in to your workspace">
    A popup opens on Slack's "Sign in to your workspace" page. Enter your workspace URL, the `your-workspace` part of `your-workspace.slack.com`, and click **Continue**. If you are already signed in, your workspaces are listed under "You're already signed in to".

    <Warning>
      Pick carefully if you belong to several workspaces. Connecting the wrong one means WPOS posts into the wrong company Slack, and the only undo is to disconnect and reconnect.
    </Warning>

    <Frame caption="Slack asks for the workspace URL.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/05-workspace.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=f914521ecc86657a1f0a302c324035d7" alt="Slack's sign in to your workspace page with a workspace URL field." width="1913" height="885" data-path="images/connectors/slack/05-workspace.png" />
    </Frame>
  </Step>

  <Step title="Allow the requested permissions">
    Slack lists what the app may do, including reading channel content and posting messages. Review and click **Allow**.
  </Step>

  <Step title="Confirm in WPOS">
    The row reads **Connected** and a green "Slack connected" banner appears in the chat.

    <Frame caption="Connected, with the confirmation banner in chat.">
      <img src="https://mintcdn.com/wpos/CKANOPF-4yzpKeQV/images/connectors/slack/06-connected.png?fit=max&auto=format&n=CKANOPF-4yzpKeQV&q=85&s=aa03d7ce4f7985868682f0b9b32b4de4" alt="The Slack row showing Connected with a Disconnect button." width="1920" height="883" data-path="images/connectors/slack/06-connected.png" />
    </Frame>
  </Step>

  <Step title="Invite the app to private channels">
    Public channels need nothing further. For a **private** channel, open it in Slack and run `/invite @WPOS`. Without this, posting to a private channel fails with a not-in-channel error.
  </Step>
</Steps>

## Troubleshooting

<AccordionGroup>
  <Accordion title="“not_in_channel”">
    The app has not been invited to that private channel. Run `/invite @WPOS` inside it.
  </Accordion>

  <Accordion title="“channel_not_found”">
    Either the channel name is wrong, or it is private and the app cannot see it. Use the exact name without the hash, and confirm the app was invited.
  </Accordion>

  <Accordion title="Installation needs admin approval">
    Your workspace restricts app installs. Ask an owner or admin to approve the request, then connect again.
  </Accordion>

  <Accordion title="Connected to the wrong workspace">
    The popup used a workspace you were already signed in to. Disconnect, then reconnect and read the workspace carefully.
  </Accordion>
</AccordionGroup>

For popup failures, expired connections, and other issues shared across every
connector, see [Introducing Connectors](/connect/connectors).