Slack Bot Integration Guide

Deploy the Superkabe Slack App to bring infrastructure observability directly to your engineering or Go-To-Market channels.

What You'll Accomplish

The Superkabe Slack integration is a two-way street. It allows you to:

Receive instant push alerts when mailboxes or domains are paused or at risk.
Get real-time recommendations in Suggest mode — so your team can act before damage occurs.
Be notified of load balancing changes, predictive risk warnings, and recovery completions.
Run interactive Slash Commands to fetch live health data without opening the dashboard.

Step 1: Connect Your Workspace

Authorize the Superkabe Slack Application to access your workspace.

1. In Superkabe, navigate to Dashboard → Settings.
2. Scroll down to the Slack Bot Integration card.
3. Click the Add to Slack button. You will be redirected to the secure Slack OAuth portal.
4. Select your Slack workspace and authorize the requested permissions (chat:write, commands, app_mentions:read).
5. Upon success, you will be redirected back to the Superkabe Settings dashboard.

Step 2: Configure Alert Channel

Choose which Slack channel receives Superkabe alerts. The bot will send a test message to verify access before saving.

1. In the Slack Integration settings card, use the channel dropdown to select a destination channel.
2. The bot automatically lists all public channels. For private channels, you must first invite the bot manually (/invite @Superkabe).
3. Click Save. A test message is sent to the channel to confirm access.
4. The integration status will show Active with a green badge once configured.

Note: If the bot loses access to the channel (deleted, archived, or permissions revoked), the status will automatically update to reflect the issue, and alerts will be paused until the channel is reconfigured.

Alerts by System Mode

The alerts you receive in Slack depend on your organization's system mode. Here's what to expect in each mode:

Observe Mode

No Slack alerts are sent. All events are logged internally for review in the audit log.

Suggest Mode

Slack alerts are sent as recommendations. No automated actions are taken — your team decides what to do. Each alert clearly states "No action taken — manual intervention recommended."

Enforce Mode

Slack alerts confirm automated actions that have already been taken (e.g., mailbox paused, domain paused, mailbox rotated).

Complete Alert Catalog

Superkabe sends the following types of Slack alerts. Each alert is color-coded by severity and deduplicated within 15-minute windows to prevent spam.

Mailbox & Domain Monitoring

Alert	Severity	Mode	Description
Mailbox Warning Recommended	Warning	Suggest	Mailbox is showing early warning signs (e.g., 3 bounces within 60 sends). Review recommended.
Mailbox Pause Recommended	Critical	Suggest	Mailbox has exceeded bounce threshold and should be paused. Manual intervention recommended.
Mailbox Paused	Critical	Enforce	Mailbox has been automatically paused and removed from all campaigns.
Domain Warning Recommended	Warning	Suggest	A percentage of domain mailboxes are unhealthy. Monitor closely.
Domain Pause Recommended	Critical	Suggest	Domain has critical health issues and should be paused. Immediate review required.
Domain Paused	Critical	Enforce	Domain has been automatically paused. All mailboxes on the domain are cascade-paused.
Campaign Pause Recommended	Critical	Suggest	Campaign should be paused due to cross-entity health correlation. Review recommended.

Recovery & Healing

Alert	Severity	Description
Mailbox Recovered	Info	Mailbox has completed the 5-phase recovery pipeline and is back in production.
Domain Recovered	Info	Domain has completed recovery and all mailboxes are operational.

Load Balancing

Alert	Severity	Description
Load Balancing Report	Warning	Summary of overloaded or underutilized mailboxes with suggested rebalancing actions.
Mailbox Added to Campaign	Info	A healthy mailbox was added to a campaign to balance sending load.
Mailbox Removed from Campaign	Warning	An overloaded or unhealthy mailbox was removed from a campaign.

Predictive Monitoring

Alert	Severity	Description
Campaign At Risk	Critical	Predictive model detects a campaign is at risk of stalling. Includes risk score, estimated time to stall, and recommended actions.
Unhealthy Mailboxes Removed	Warning	Predictive action automatically removed unhealthy mailboxes from a campaign to prevent stalling.
Healthy Mailboxes Added	Info	Predictive action added healthy standby mailboxes to a campaign to maintain sending capacity.

Alert Features

Deduplication

Alerts are deduplicated within 15-minute windows. If the same event fires multiple times (e.g., repeated bounce processing), you'll only receive one Slack message per window.

Color-Coded Severity

Messages use Slack Block Kit with color-coded sidebars: green for info, yellow for warnings, and red for critical alerts.

Non-Blocking

Alert delivery never blocks core operations. If Slack is unreachable or rate-limited, the system retries with exponential backoff (up to 3 attempts) and continues processing.

Auto-Freeze on Errors

If the bot token is revoked, the channel is deleted, or permissions are removed, the integration status automatically updates and alerts pause until you reconfigure.

Slash Commands

The Superkabe bot listens for interactive commands in any channel it is invited to:

/superkabe status <domain>
Returns the health status, bounce rate, and active mailbox count for a specific domain.
Example: /superkabe status superkabe.ai
Response: "superkabe.ai is HEALTHY. 4/4 mailboxes operational. 2.1% bounce rate over last 100 sends."
/superkabe mailbox <email>
Fetches the current status, health score, and recovery phase of a specific mailbox.
Example: /superkabe mailbox john@superkabe.ai
Response: "john@superkabe.ai — Status: HEALTHY, Score: 85, Phase: active, Sends: 142, Bounces: 2"
/superkabe org
Returns an executive summary of your organization's infrastructure — total mailboxes, domains, active campaigns, and any critical risks.
Example: /superkabe org
Response: "12 mailboxes across 3 domains. 5 active campaigns. 1 mailbox in recovery. System mode: Suggest."

Security

Encrypted at rest: Your Slack bot token is encrypted using AES-256-GCM before being stored. It is never logged or exposed in API responses.
OAuth 2.0: Connection uses Slack's official OAuth 2.0 flow. No passwords or tokens are manually entered.
Webhook verification: All incoming Slack events and commands are verified using Slack's signing secret to prevent spoofing.
Isolated decryption: Token decryption runs in an isolated scope, separate from web request threads, to prevent accidental token leakage.

Disconnecting

To disconnect the Slack integration:

1. Navigate to Dashboard → Settings.
2. In the Slack Integration card, click Disconnect.
3. Confirm the action. The bot token will be revoked and the integration record removed.
4. You can reconnect at any time by clicking Add to Slack again.

Next Steps

Your team is now synced with Superkabe's real-time analysis engine. Check out: