Overview
StatusStack integrates with popular communication and collaboration tools to deliver notifications exactly where your team works.Available Integrations
Slack
Post alerts to Slack channels with rich formatting
Discord
Send notifications to Discord servers
Microsoft Teams
Deliver adaptive cards to Teams channels
Send email notifications to individuals or groups
Webhooks
Custom integrations with any webhook-enabled service
Browser Extension
Chrome and Edge toolbar status check and anonymous outage reports
Integration Categories
Team Communication
Real-time alerts to team chat platforms:Direct Notifications
Personal notification channels:Custom Integrations
Build your own integrations:PSA ticket connectors
MSP ticket open and close is live for ConnectWise. Connect it from the MSP Console under Settings → Integrations, then use MSP Automations to create tickets on incidents. Datto Autotask PSA and HaloPSA ticket connectors are coming soon (early access). Marketing pages describe the intended workflow, but there is no in-app Autotask or HaloPSA ticket connector to configure today. You can still use StatusStack for vendor monitoring, white-label status pages, and per-client reports while those connectors are in development. MSP documentation import (Hudu / IT Glue) is a separate integration type — see Hudu & IT Glue Stack Import.Quick Setup Guide
Step 1: Choose Your Integration
Consider your team’s workflow:We use Slack for everything
We use Slack for everything
Recommended: Slack integrationSetup:
- Create Slack webhook
- Add to notification rule
- Test alert
We're on Microsoft 365
We're on Microsoft 365
Recommended: Microsoft Teams integrationSetup:
- Create Teams webhook
- Configure adaptive card
- Test delivery
We need SMS for critical alerts
We need SMS for critical alerts
Recommended: Twilio SMS integrationSetup:
- Sign up for Twilio
- Add credentials to StatusStack
- Configure phone numbers
- Test SMS
We use PagerDuty
We use PagerDuty
Recommended: Webhook integrationSetup:
- Get PagerDuty webhook URL
- Create webhook integration
- Map event types
- Test routing
Step 2: Create Notification Rule
Once integration is configured:1
Navigate to Notifications
Dashboard → Settings → Notifications
2
Create Rule
Click “Create Notification Rule”
3
Select Integration
Choose your configured integration channel
4
Configure Triggers
Set when to send alerts:
- Component becomes Critical
- Monitor goes down
- Incident created
5
Test
Send test notification to verify setup
Step 3: Test and Refine
Initial testing:- Send test notification
- Verify message format
- Check delivery time
- Confirm recipient list
- Adjust trigger conditions
- Fine-tune alert levels
- Optimize message content
- Set up rate limiting
Integration Comparison
Feature Matrix
Use Case Recommendations
- Tech Startups
- Enterprise
- Gaming/Community
- MSPs
Primary: Slack
- Real-time team collaboration
- Rich formatting and threading
- Easy setup
- Distribution lists
- Stakeholder updates
- On-call management
- Escalation policies
Multi-Channel Strategy
Layered Alert Approach
Tier 1: Informational- Channels: Email (digest), Dashboard
- Frequency: Daily summary
- Examples: Resolved incidents, scheduled maintenance
- Channels: Slack, Teams, Email
- Frequency: Immediate
- Examples: Performance degradation, partial outages
- Channels: Slack + Email + SMS + PagerDuty
- Frequency: Immediate
- Examples: Complete service outages, security incidents
Example Configuration
Best Practices
Choose the Right Channel
Choose the Right Channel
Match channel to urgency:✅ Slack/Teams for:
- Real-time team coordination
- Working hours alerts
- Collaborative response
- Formal notifications
- Stakeholder updates
- Audit trail
- Critical outages only
- On-call escalation
- After-hours emergencies
- Third-party integration
- Incident management tools
- Custom automation
Avoid Alert Fatigue
Avoid Alert Fatigue
Don’t spam your team:❌ Bad:
- Every status change → Slack
- Info alerts → SMS
- Staging issues → Critical channel
- Critical production → Multiple channels
- Degraded production → Slack only
- Staging issues → Email digest
- Info updates → Dashboard only
Test Before Relying On
Test Before Relying On
Verify integrations work:Weekly:
- Send test notification
- Verify delivery time
- Check formatting
- Confirm recipients
- Review notification logs
- Check for failed deliveries
- Update contact lists
- Validate webhooks still work
Use Multiple Channels for Critical
Use Multiple Channels for Critical
Redundancy prevents missed alerts:Single channel:Multi-channel:
Respect Rate Limits
Respect Rate Limits
Each service has limits:
StatusStack automatically:
- Respects rate limits
- Queues messages
- Retries failures
Troubleshooting
Integration Not Working
Common issues:Webhook URL Invalid
Webhook URL Invalid
Symptoms:
- “Invalid webhook URL” error
- No messages delivered
- Verify webhook URL is correct
- Check for extra spaces
- Ensure HTTPS (not HTTP)
- Test webhook in browser
Messages Not Appearing
Messages Not Appearing
Check:
- Notification rule is active
- Triggers are configured
- Channel is selected
- Test notification works
- View notification logs
- Check delivery status
- Verify channel permissions
Delayed Notifications
Delayed Notifications
Possible causes:
- Service rate limiting
- Network latency
- Queue backlog
- Slack: < 5 seconds
- Discord: < 5 seconds
- Teams: < 10 seconds
- Email: < 30 seconds
- SMS: < 10 seconds
Next Steps
Choose your integration to get started:Slack Integration
Set up Slack notifications in 2 minutes
Discord Integration
Configure Discord webhooks and embeds
Microsoft Teams
Send adaptive cards to Teams
Email Notifications
Configure email delivery
SMS Alerts
Set up Twilio SMS notifications
Custom Webhooks
Build custom integrations
Browser Extension
Check live status from Chrome or Edge

