Skip to content

Channels: Slack

Slack is a Tier 1 channel. Wayland uses a native Slack bot. You can run it in Socket Mode, which needs no public URL, or with the Events API if you already have a stable HTTPS endpoint.

Before you start (prerequisites and accounts)

Section titled “Before you start (prerequisites and accounts)”
  • A Slack workspace where you can install apps.
  • The Wayland desktop app running with a model provider connected.

Create the credentials (on the provider side)

Section titled “Create the credentials (on the provider side)”
  1. Go to the Slack API site and create a new app for your workspace.
  2. Add the bot scopes your use needs, then install the app to the workspace. This produces a Bot token (starts with xoxb-).
  3. For Socket Mode, enable Socket Mode and create an App token (starts with xapp-).
  4. From the app’s Basic Information, copy the Signing secret.

Connect it in Wayland (Settings -> Channels -> Slack)

Section titled “Connect it in Wayland (Settings -> Channels -> Slack)”
  1. Open Settings -> Channels and choose Slack.
  2. Pick the Transport: Socket Mode or Events API.
  3. Paste the Bot token.
  4. For Socket Mode, paste the App token. For the Events API, provide the Signing secret.
  5. Save.

Verify (status goes from idle to connected, send a test message)

Section titled “Verify (status goes from idle to connected, send a test message)”

After saving, the status moves from idle to connected. Invite the bot to a channel or send it a direct message, then confirm a reply. If you chose the Events API, point your Slack event subscription at the webhook URL shown on the page.

Set the assistant and default model on the Slack page. Inbound Slack messages are routed to that assistant.

A missing scope or an incorrect signing secret is the usual cause of failures. See Channel Connection Issues.