Docs

Slack Integration

Audit Slack workspace security and receive threat alerts via webhook.

#Setup

  • 1

    Create a Slack app and bot token

    Go to api.slack.com/apps → Create New App → From scratch. Add the channels:read, channels:join, groups:read, and users:read bot scopes, install the app to your workspace, and copy the Bot User OAuth Token (xoxb-...).
  • 2

    (Optional) Create an incoming webhook for alerts

    In your Slack workspace, go to apps.slack.com/apps → Incoming Webhooks → Add to Slack, pick the channel for security alerts, and copy the webhook URL (https://hooks.slack.com/services/...). Paste it into the Webhook URL (for alerts) field when connecting.
  • 3

    Connect in Vergate

    Go to Integrations, click Connect on Slack, and paste the bot token (and webhook URL if you want alerts).
  • 4

    Verify

    Click Test Connection — Vergate calls the Slack auth.test endpoint.

    • #Threat Alerts

    When a Webhook URL is set, Slack also acts as a notification channel: monitoring threat re-scans that find new or regressed findings post a security alert to your channel. Alerts are diff-based — you only get pinged when something actually changed. Slack uses the webhook URL for alert delivery only; the bot token is never used for sending.

    #What It Scans

    Token validity — Does the bot token authenticate?
    Token type — Is it a bot token (xoxb-) or a user token?
    Channel exposure — How many public channels can the bot see?
    Message access — Is the bot a member of channels it can read, or does it have unrestricted access?

    Warning. Never use a user OAuth token (xoxp-) for scanning — it exposes the user's full workspace access. Bot tokens are scoped and revocable.