Skip to content

Resources / Integrations / Slack

Slack

Weekly prompts and new-intro posts to a channel you choose, plus an optional directory and direct-message grant.

Last verified against our product: October 4, 2026

Availability

Available in the admin console

How an admin connects it

Two separate OAuth grants. The first is for channel posts; the second is optional, for directory and direct messages.

Who can set it up: Organization admin.

  1. Notifications: in the admin console, open the Slack card, click Connect, and choose the channel Slack should post to.
  2. Directory and direct messages (optional): click the separate directory connect and approve the read-and-message request.

Permissions requested

Permission or scopeWhat it allows
incoming-webhookPost to the one channel you pick during install. Notifications grant.
users:readList workspace members. Directory grant.
users:read.emailRead member email so we can match Slack people to Mucho Gusto members. Directory grant.
chat:writeSend direct messages such as meeting-prep prompts. Directory grant.

Workspaces that connected the directory grant before chat:write was added keep the narrower scope until they reconnect. We request no channel-history, message-content or file scopes.

Data we read

Read

  • Notifications grant: the workspace name and the chosen channel name
  • Directory grant: each member's email and real name

Not read

  • Messages, channel history or files
  • Deleted, bot, and restricted or guest accounts (skipped)
  • Job titles or reporting lines (Slack does not supply them to us)

How the data is used

  • A weekly prompt (Mondays, 15:00 UTC) and new-intro posts to your chosen channel.
  • The directory grant matches Slack people to members by email so meeting-prep prompts can arrive as a Slack direct message.

Sync frequency

Channel posts are event-driven plus the Monday 15:00 UTC prompt. The directory grant is matched in the nightly 04:00 UTC resync.

Disconnecting and purging data

How: Admin console, Slack card, Disconnect (and Disconnect directory for the second grant).

  • Disconnecting notifications deletes our stored webhook and channel.
  • Disconnecting the directory grant deletes our stored bot token.
  • Also remove the app from your Slack workspace settings to revoke it on Slack's side.

What remains: Previously stored Slack-to-member mappings are not removed by disconnecting. To have previously synced data removed as well, email [email protected] and we will handle it case by case; there is no self-service purge today.

Back to all integrations

Questions or a correction? [email protected]. See also: Security, Subprocessors, Privacy, Terms.