Hermes BibleUnofficial Docs
← All docs Docs / Messaging Platforms

Slack

Slack Setup Connect Hermes Agent to Slack as a bot using Socket Mode. Socket Mode uses WebSockets instead of public HTTP endpoints, so your Hermes instance does

Messaging Platforms
Section
Messaging Platforms
Source
hermesbible.com/docs/user-guide/messaging/slack

Slack Setup Connect Hermes Agent to Slack as a bot using Socket Mode. Socket Mode uses WebSockets instead of public HTTP endpoints, so your Hermes instance does

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Overview
  2. Step 1: Create a Slack App
  3. Option A: From a Hermes-generated manifest (recommended)
  4. Option B: From scratch (manual)
  5. Step 2: Configure Bot Token Scopes
  6. Step 3: Enable Socket Mode
  7. Step 4: Subscribe to Events
  8. Step 5: Enable the Messages Tab
  9. Step 6: Install App to Workspace
  10. Step 7: Find User IDs for the Allowlist
  11. Step 8: Configure Hermes
  12. Step 9: Invite the Bot to Channels
  13. Slash Commands
  14. Refreshing slash commands after updates

Section map

Overview

Maps overview to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 1: Create a Slack App

Maps step 1: create a slack app to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Option A: From a Hermes-generated manifest (recommended)

Maps option a: from a hermes-generated manifest (recommended) to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Option B: From scratch (manual)

Maps option b: from scratch (manual) to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 2: Configure Bot Token Scopes

Maps step 2: configure bot token scopes to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 3: Enable Socket Mode

Maps step 3: enable socket mode to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 4: Subscribe to Events

Maps step 4: subscribe to events to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 5: Enable the Messages Tab

Maps step 5: enable the messages tab to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Messaging Platforms doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Overview, Step 1: Create a Slack App, Option A: From a Hermes-generated manifest (recommended), Option B: From scratch (manual), Step 2: Configure Bot Token Scopes. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: slack, setup, connect, socket, mode.. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitMessaging Platforms documentation

Use when you need orientation for slack before applying exact upstream commands.

Verify firstOverview

Open the source anchor for Overview and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Messaging Platforms, then open the linked source page for exact current syntax.
  2. Start with the source section for Overview; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Step 1: Create a Slack App if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page