> ## Documentation Index
> Fetch the complete documentation index at: https://docs.statusstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Overview

> Connect StatusStack with your favorite tools and services

## Overview

StatusStack integrates with popular communication and collaboration tools to deliver notifications exactly where your team works.

***

## Available Integrations

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Post alerts to Slack channels with rich formatting
  </Card>

  <Card title="Discord" icon="discord" href="/integrations/discord">
    Send notifications to Discord servers
  </Card>

  <Card title="Microsoft Teams" icon="microsoft" href="/integrations/microsoft-teams">
    Deliver adaptive cards to Teams channels
  </Card>

  <Card title="Email" icon="envelope" href="/integrations/email">
    Send email notifications to individuals or groups
  </Card>

  <Card title="Webhooks" icon="webhook" href="/integrations/webhooks">
    Custom integrations with any webhook-enabled service
  </Card>
</CardGroup>

***

## Integration Categories

### Team Communication

Real-time alerts to team chat platforms:

| Integration         | Setup Time | Best For                           |
| ------------------- | ---------- | ---------------------------------- |
| **Slack**           | 2 minutes  | Modern teams, tech companies       |
| **Discord**         | 2 minutes  | Gaming, communities, tech startups |
| **Microsoft Teams** | 3 minutes  | Enterprise, Microsoft 365 users    |

### Direct Notifications

Personal notification channels:

| Integration | Setup Time | Best For                      |
| ----------- | ---------- | ----------------------------- |
| **Email**   | 1 minute   | Universal, distribution lists |

### Custom Integrations

Build your own integrations:

| Integration  | Setup Time   | Best For                         |
| ------------ | ------------ | -------------------------------- |
| **Webhooks** | 2-10 minutes | PagerDuty, Datadog, custom tools |

***

## Quick Setup Guide

### Step 1: Choose Your Integration

Consider your team's workflow:

<AccordionGroup>
  <Accordion title="We use Slack for everything">
    **Recommended:** Slack integration

    **Setup:**

    1. Create Slack webhook
    2. Add to notification rule
    3. Test alert

    **Time:** 2 minutes

    [Slack Setup Guide →](/integrations/slack)
  </Accordion>

  <Accordion title="We're on Microsoft 365">
    **Recommended:** Microsoft Teams integration

    **Setup:**

    1. Create Teams webhook
    2. Configure adaptive card
    3. Test delivery

    **Time:** 3 minutes

    [Teams Setup Guide →](/integrations/microsoft-teams)
  </Accordion>

  <Accordion title="We need SMS for critical alerts">
    **Recommended:** Twilio SMS integration

    **Setup:**

    1. Sign up for Twilio
    2. Add credentials to StatusStack
    3. Configure phone numbers
    4. Test SMS

    **Time:** 5 minutes

    [SMS Setup Guide →](/integrations/sms)
  </Accordion>

  <Accordion title="We use PagerDuty">
    **Recommended:** Webhook integration

    **Setup:**

    1. Get PagerDuty webhook URL
    2. Create webhook integration
    3. Map event types
    4. Test routing

    **Time:** 5 minutes

    [Webhook Setup Guide →](/integrations/webhooks)
  </Accordion>
</AccordionGroup>

### Step 2: Create Notification Rule

Once integration is configured:

<Steps>
  <Step title="Navigate to Notifications">
    Dashboard → **Settings** → **Notifications**
  </Step>

  <Step title="Create Rule">
    Click **"Create Notification Rule"**
  </Step>

  <Step title="Select Integration">
    Choose your configured integration channel
  </Step>

  <Step title="Configure Triggers">
    Set when to send alerts:

    * Component becomes Critical
    * Monitor goes down
    * Incident created
  </Step>

  <Step title="Test">
    Send test notification to verify setup
  </Step>
</Steps>

### Step 3: Test and Refine

**Initial testing:**

1. Send test notification
2. Verify message format
3. Check delivery time
4. Confirm recipient list

**Refinement:**

1. Adjust trigger conditions
2. Fine-tune alert levels
3. Optimize message content
4. Set up rate limiting

***

## Integration Comparison

### Feature Matrix

| Feature                | Slack      | Discord  | Teams     | Email      | Webhooks |
| ---------------------- | ---------- | -------- | --------- | ---------- | -------- |
| **Rich formatting**    | ✅          | ✅        | ✅         | ✅          | Varies   |
| **Inline images**      | ✅          | ✅        | ✅         | ✅          | Varies   |
| **Threaded alerts**    | ✅          | ❌        | ❌         | ✅          | ❌        |
| **Mentions**           | ✅          | ✅        | ✅         | ❌          | ❌        |
| **Actionable buttons** | ⚠️ Limited | ❌        | ✅         | ⚠️ Limited | Varies   |
| **Free tier**          | ✅          | ✅        | ✅         | ✅          | ✅        |
| **Rate limits**        | Yes        | Yes      | Yes       | Yes        | Varies   |
| **Delivery speed**     | \< 5 sec   | \< 5 sec | \< 10 sec | \< 30 sec  | Varies   |

### Use Case Recommendations

<Tabs>
  <Tab title="Tech Startups">
    **Primary:** Slack

    * Real-time team collaboration
    * Rich formatting and threading
    * Easy setup

    **Secondary:** Email

    * Distribution lists
    * Stakeholder updates

    **Critical Alerts:** PagerDuty (webhook)

    * On-call management
    * Escalation policies
  </Tab>

  <Tab title="Enterprise">
    **Primary:** Microsoft Teams

    * Microsoft 365 integration
    * Enterprise compliance
    * Adaptive cards

    **Secondary:** Email

    * Formal notifications
    * Audit trail

    **Critical Alerts:**  Email

    * On-call engineers
    * Management escalation
  </Tab>

  <Tab title="Gaming/Community">
    **Primary:** Discord

    * Community-focused
    * Role mentions
    * Rich embeds

    **Critical Alerts:** Email

    * Server outages
    * Critical infrastructure
  </Tab>

  <Tab title="MSPs">
    **Internal:** MS Teams

    * MSP team collaboration
    * Centralized alerts

    **Clients:** Email

    * Professional communication
    * Client stakeholders

    **Critical:** Multi-channel

    * MS Teams + Email
    * Redundant delivery
  </Tab>
</Tabs>

***

## Multi-Channel Strategy

### Layered Alert Approach

**Tier 1: Informational**

* Channels: Email (digest), Dashboard
* Frequency: Daily summary
* Examples: Resolved incidents, scheduled maintenance

**Tier 2: Degraded Services**

* Channels: Slack, Teams, Email
* Frequency: Immediate
* Examples: Performance degradation, partial outages

**Tier 3: Critical Outages**

* Channels: Slack + Email + SMS + PagerDuty
* Frequency: Immediate
* Examples: Complete service outages, security incidents

### Example Configuration

```yaml theme={null}
Rule: "Info Updates"
  Triggers: Component recovers, Maintenance scheduled
  Channels: Email (daily digest)

Rule: "Degraded Warnings"
  Triggers: Component degraded, Monitor slow
  Channels: Slack #alerts

Rule: "Critical Alerts"
  Triggers: Component critical, Monitor down
  Channels:
    - Slack #critical-alerts (@channel mention)
    - Email ops@company.com
    - PagerDuty On-Call Team
    - SMS (on-call engineer)
```

***

## Best Practices

<AccordionGroup>
  <Accordion title="Choose the Right Channel">
    **Match channel to urgency:**

    ✅ **Slack/Teams** for:

    * Real-time team coordination
    * Working hours alerts
    * Collaborative response

    ✅ **Email** for:

    * Formal notifications
    * Stakeholder updates
    * Audit trail

    ✅ **SMS** for:

    * Critical outages only
    * On-call escalation
    * After-hours emergencies

    ✅ **Webhooks** for:

    * Third-party integration
    * Incident management tools
    * Custom automation
  </Accordion>

  <Accordion title="Avoid Alert Fatigue">
    **Don't spam your team:**

    ❌ Bad:

    * Every status change → Slack
    * Info alerts → SMS
    * Staging issues → Critical channel

    ✅ Good:

    * Critical production → Multiple channels
    * Degraded production → Slack only
    * Staging issues → Email digest
    * Info updates → Dashboard only
  </Accordion>

  <Accordion title="Test Before Relying On">
    **Verify integrations work:**

    Weekly:

    * [ ] Send test notification
    * [ ] Verify delivery time
    * [ ] Check formatting
    * [ ] Confirm recipients

    Monthly:

    * [ ] Review notification logs
    * [ ] Check for failed deliveries
    * [ ] Update contact lists
    * [ ] Validate webhooks still work
  </Accordion>

  <Accordion title="Use Multiple Channels for Critical">
    **Redundancy prevents missed alerts:**

    Single channel:

    ```yaml theme={null}
    Critical Alert → Slack only
    Risk: Slack outage = No alerts
    ```

    Multi-channel:

    ```yaml theme={null}
    Critical Alert →
      - Slack #alerts
      - Email ops@company.com
      - SMS on-call engineer
      - PagerDuty incident
    Risk: Minimized
    ```
  </Accordion>

  <Accordion title="Respect Rate Limits">
    **Each service has limits:**

    | Service    | Rate Limit         | How to Handle             |
    | ---------- | ------------------ | ------------------------- |
    | Slack      | 1/second           | Group alerts, use threads |
    | Discord    | 5/5 seconds        | Batch updates             |
    | Teams      | 4/second           | Queue messages            |
    | Email      | Varies by provider | Use digest mode           |
    | Twilio SMS | Varies by plan     | Critical only             |

    **StatusStack automatically:**

    * Respects rate limits
    * Queues messages
    * Retries failures
  </Accordion>
</AccordionGroup>

***

## Troubleshooting

### Integration Not Working

**Common issues:**

<AccordionGroup>
  <Accordion title="Webhook URL Invalid">
    **Symptoms:**

    * "Invalid webhook URL" error
    * No messages delivered

    **Solutions:**

    1. Verify webhook URL is correct
    2. Check for extra spaces
    3. Ensure HTTPS (not HTTP)
    4. Test webhook in browser
  </Accordion>

  <Accordion title="Messages Not Appearing">
    **Check:**

    1. Notification rule is active
    2. Triggers are configured
    3. Channel is selected
    4. Test notification works

    **Debug:**

    * View notification logs
    * Check delivery status
    * Verify channel permissions
  </Accordion>

  <Accordion title="Delayed Notifications">
    **Possible causes:**

    1. Service rate limiting
    2. Network latency
    3. Queue backlog

    **Normal latency:**

    * Slack: \< 5 seconds
    * Discord: \< 5 seconds
    * Teams: \< 10 seconds
    * Email: \< 30 seconds
    * SMS: \< 10 seconds
  </Accordion>
</AccordionGroup>

***

## Next Steps

Choose your integration to get started:

<CardGroup cols={2}>
  <Card title="Slack Integration" icon="slack" href="/integrations/slack">
    Set up Slack notifications in 2 minutes
  </Card>

  <Card title="Discord Integration" icon="discord" href="/integrations/discord">
    Configure Discord webhooks and embeds
  </Card>

  <Card title="Microsoft Teams" icon="microsoft" href="/integrations/microsoft-teams">
    Send adaptive cards to Teams
  </Card>

  <Card title="Email Notifications" icon="envelope" href="/integrations/email">
    Configure email delivery
  </Card>

  <Card title="SMS Alerts" icon="message" href="/integrations/sms">
    Set up Twilio SMS notifications
  </Card>

  <Card title="Custom Webhooks" icon="webhook" href="/integrations/webhooks">
    Build custom integrations
  </Card>
</CardGroup>