Slack Integration

Receive real-time backup notifications directly in your Slack workspace. Get instant alerts for backup completions, failures, security events, and health warnings.

v1.0.0Updated 2026-01-01

Features

  • Real-time notifications via Slack webhooks
  • Rich message formatting with Slack Block Kit
  • Customizable event types (success, failures, security alerts)
  • Channel override for routing to specific channels
  • Interactive buttons for quick actions
  • Test webhook before saving configuration

Quick Setup

Step 1: Create Slack Webhook

  1. Go to api.slack.com/apps
  2. Click "Create New App""From scratch"
  3. Name it "LOX Backups" and select your workspace
  4. Go to "Incoming Webhooks" in the sidebar
  5. Toggle "Activate Incoming Webhooks" to On
  6. Click "Add New Webhook to Workspace"
  7. Select the channel for notifications and click "Allow"
  8. Copy the webhook URL (starts with https://hooks.slack.com/...)

Step 2: Configure in LOX

  1. Go to SettingsNotifications in your LOX dashboard
  2. Paste your Slack webhook URL
  3. Select which events you want to receive
  4. Click "Test Webhook" to verify it works
  5. Enable the integration and save

Pro Tip

Create a dedicated #lox-backups channel to keep backup notifications organized and easy to monitor.

Event Types

EventDescription
backup_completedBackup finished successfully
backup_failedBackup failed with error
verification_passedBackup integrity verified
verification_failedBackup verification failed
quarantineBackup quarantined (malware/threat detected)
health_warningHealth score dropped below threshold
restore_readyBackup is ready for download/restore

API Configuration

You can also configure Slack notifications via the API:

Get Current Configuration

curl -X GET "https://backlox.com/api/v1/notifications/slack" \
  -H "Authorization: Bearer ${LOX_API_KEY}"

Update Configuration

curl -X PUT "https://backlox.com/api/v1/notifications/slack" \
  -H "Authorization: Bearer ${LOX_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "webhook_url": "https://hooks.slack.com/services/T.../B.../...",
    "channel": "#lox-backups",
    "enabled": true,
    "events": ["backup_completed", "backup_failed", "quarantine", "health_warning"]
  }'

Test Webhook

curl -X POST "https://backlox.com/api/v1/notifications/slack/test" \
  -H "Authorization: Bearer ${LOX_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "webhook_url": "https://hooks.slack.com/services/T.../B.../...",
    "channel": "#lox-backups"
  }'

Message Examples

Backup Completed

:white_check_mark: Backup Completed
Backup: wordpress-daily-20251225
Size: 156.42 MB
Status: completed
Distributed: Yes
UUID: abc123... | Tenant: My Company

Quarantine Alert

:biohazard_sign: Backup Quarantined
:rotating_light: Security Alert
Backup suspicious-file-20251225 has been quarantined.
Reason: Malware detected (Eicar-Test-Signature)
Malware Scan: Failed
Integrity Check: Passed
Tenant: My Company | Action Required: Review this backup immediately

Health Warning

:warning: Health Score Warning
Your backup health score has dropped to 65/100
Issues Detected:
  • No backup in last 48 hours
  • Storage usage at 85%
View Dashboard

Best Practices

Avoid notification fatigue

Consider only enabling failure and security events in production. Backup completed events can be noisy for frequent backups.

Use dedicated channels

Route LOX notifications to a dedicated channel like #ops-backupsor #alerts-lox.

Keep webhook URL secure

Treat your webhook URL like a password. Anyone with the URL can post to your channel. Rotate it if compromised.

Troubleshooting

Messages not appearing

Verify the webhook URL is correct and the Slack app is still active. Use the test endpoint to verify connectivity.

channel_not_found error

The channel override you specified doesn't exist or the bot doesn't have access. Make sure to include the # prefix.

Rate limits

Slack webhooks have rate limits (1 message per second). LOX batches notifications to avoid hitting limits.