Skip to content
murmurd docs

Slack Integration

Slack is available on Pro, Enterprise, and active Pro trials. It adds the fastest delivery path for check-ins and lets teams act without leaving Slack.

Features

  • daily check-in prompts via DM
  • interactive actions to submit, skip, or pause reminders
  • optional reply-based Slack check-ins
  • /escalate
  • /priority
  • Friday division digests for Team Leaders and Team Managers

Install

Start from the Murmurd install link:

If your organization requires a technical or security review before approving Slack apps, share the Slack enterprise approval guide.

Connecting Slack

Connect the workspace from organization settings. Murmurd also supports a linking-code flow when an IT admin needs to finish the Slack authorization outside the product setup session.

Linking User Accounts

Murmurd can auto-match users by email after a workspace is linked. If a user is still unmatched, they can add their Slack member ID in Account Settings.

Data Access Boundary

  • Murmurd does not read employee-to-employee direct messages.
  • Murmurd does not read public or private channel history.
  • Murmurd only processes direct messages sent to the Murmurd bot so users can reply to Murmurd check-ins.
  • Murmurd reads Slack user/profile directory data for account linking and admin setup flows.

Slack Scopes

  • chat:write, im:write for check-in DMs, reminders, and leadership digests
  • commands for /escalate, /priority, and modal flows
  • users:read, users:read.email for account linking and admin setup flows
  • team:read for connected workspace metadata
  • im:history only for reply-based check-ins sent to the Murmurd bot

Security

  • Slack tokens are encrypted at rest with AES-256-GCM.
  • Incoming Slack requests are verified with HMAC-SHA256 signatures and timestamp checks.
  • If Slack is disconnected, Murmurd falls back to email and web delivery.
  • Murmurd does not store channel message history or a permanent full copy of the Slack directory.