Slack and Teams Integration

This guide covers secure setup for Slack and Microsoft Teams notifications, including recommended channel topology and delivery validation.

Slack Setup

Go to Settings → Integrations → Slack.
Click Authorize and approve the FixFast.ai app in your Slack workspace.
Select one or more channels; enable thread replies for noisy alerts to reduce channel volume.
Save and send a test notification.

Recommended Slack Topology

#fixfast-prod for production alerts and RCA summaries.
#fixfast-sandbox for test traffic.
Private channels for regulated data when needed; ensure app access is allowed.

Slack Payload Example (Anomaly)

{
  "event": "anomaly.detected",
  "org_id": "org_123",
  "workspace": "prod",
  "severity": "high",
  "summary": "CPU saturation in cluster prod-eu",
  "top_drivers": [
    {"dimension": "namespace", "value": "payments", "impact": 0.37},
    {"dimension": "node", "value": "ip-10-0-8-21", "impact": 0.24}
  ],
  "run_id": "run_abc",
  "timestamp": "2024-05-10T12:00:00Z"
}

Troubleshooting Slack

If authorization fails, confirm the Slack admin has allowed the app and scopes.
If messages do not appear, verify the app was added to the target channel.
Check the delivery log in FixFast.ai (per destination) for HTTP 4xx/5xx errors.

Microsoft Teams Setup

In Teams, create an Incoming Webhook connector for the target channel.
Copy the webhook URL.
In FixFast.ai Settings → Integrations → Teams, paste the URL and set a signing secret.
Send a test message and confirm it arrives.

Teams Payload Shape

Teams cards contain the same fields as Slack but wrapped in an Adaptive Card payload. Ensure the webhook accepts JSON and permits cards.

Reliability and Retries

Both Slack and Teams deliveries inherit the webhook retry policy (exponential backoff, up to 5 attempts, 30-second initial delay).
Non-2xx responses trigger retries; 410/404 are treated as permanent failures and disable the destination until revalidated.
Delivery logs show request/response status, elapsed time, and signature verification status.

Security Considerations

Signing secrets are stored in a vault and never returned after creation.
Rotate secrets quarterly; use different secrets per workspace.
Limit channel membership for production notifications; audit regularly.

docs/integrations/webhooks.md for generic webhook schema and signature verification.
docs/security/overview.md for encryption, isolation, and retention controls.

slack.md