Skip to main content
Runlayer can send notifications to a shared Slack channel and direct messages to individual users. Channel notifications alert admins to events that need attention — security violations, new connector requests, access requests. DMs notify users when their requests are approved or rejected. Slack Integration settings showing a connected workspace with notification channel configured

​
What Gets Notified

​
Channel Notifications

Sent to your configured notification channel:
EventDescription
New connector requestA user requests a new MCP server to be added
Access requestA user requests access to an existing MCP server
Security violationToolGuard detects a policy violation or security threat
Each notification includes a direct link to review the event in Runlayer. Example Slack notification for a security violation alert

​
Direct Messages

Sent to individual users via DM:
EventDescription
Request approvedYour connector or access request was approved
Request rejectedYour connector or access request was rejected
Config token expiredYour Slack configuration token needs to be refreshed
DM notifications require the user’s Slack email to match their Runlayer email. Runlayer looks up and caches the Slack user ID automatically.

​
Setup

All Slack configuration lives in Admin → Settings → Slack Integration.
1

Generate a Configuration Token

Go to api.slack.com/apps, scroll to Your App Configuration Tokens, click Generate Token, and select your workspace. Copy the Refresh Token (starts with xoxe-).Slack App Configuration Tokens page with Generate Token and Copy buttons highlighted
Configuration tokens are single-use. Do not paste the same token into multiple environments — each use permanently invalidates the previous token.
2

Save the token in Runlayer

In Admin → Settings → Slack Integration, expand the Configuration Tokens section, click Configure, paste the refresh token, and click Save Token.Configuration Token setup form showing where to paste the refresh token
3

Create the Notifications Slack App

Click Create Slack App in the Notifications section. Runlayer creates a Slack app with the correct permissions and redirects you to Slack for OAuth authorization.
4

Authorize in Slack

Review the permissions and click Allow. You’ll be redirected back to Runlayer.
5

Select a notification channel

Choose the channel where notifications should be sent. Only channels the Slack app has been invited to will appear.
To use a private channel, first invite the app by sending /invite @Runlayer in that channel.
6

Send a test message

Click Send Test to verify everything works. A test notification will appear in the selected channel.

​
Enterprise Grid

For Slack Enterprise Grid installations, an additional Workspace selector appears after connecting. Select the workspace first, then choose a channel within it. The notification channel and workspace are saved together.

​
Managing the Integration

​
Changing the notification channel

Select a different channel from the dropdown at any time. The change takes effect immediately.

​
Disconnecting

Click Disconnect next to the connection status. This revokes the bot token and stops all notifications. The Slack app itself remains in your workspace — you can reconnect by clicking Connect to Slack again.

​
Removing the Slack app entirely

With a valid configuration token, click Delete App to remove the Slack app from your workspace completely.
If the app was created by a different Slack admin than the one who configured the token, Runlayer cannot auto-update or delete the app. You’ll see a warning — manage it directly at api.slack.com/apps.

​
Agent Slack Apps

Separate from notifications, each agent can have its own Slack app for @mentions and DMs. These are configured per-agent in Build → [Agent] → Slack and require the same configuration token. See the Slack Integration section in Settings for a list of all connected agent apps.

​
Troubleshooting

The Slack app can only see channels it’s been invited to. For public channels, the app should see them automatically. For private channels, send /invite @Runlayer in the channel first, then refresh the page.
Check that:
  • The Slack app is still authorized (not uninstalled from Slack)
  • A notification channel is selected
  • The app hasn’t been removed from the channel
If the app’s token was revoked (e.g., someone uninstalled it from Slack), Runlayer automatically marks the connection as disconnected. Reconnect to restore notifications.
DM notifications require the recipient’s email in Runlayer to match their email in Slack. If emails don’t match, the Slack user lookup fails silently and the DM is skipped.
This appears when the Slack app was created by a different admin than the one whose configuration token is currently saved. Runlayer needs the original creator’s token to update app manifests. Either:
  • Have the original creator generate a new configuration token, or
  • Delete the app and recreate it with the current admin’s token
Slack configuration tokens expire periodically. When this happens, the admin who configured the token receives a DM (if Slack is still connected) and the token is automatically removed. Generate a new token at api.slack.com/apps and save it in Settings.