Overview
IncidentFox integrates with your existing collaboration and incident management tools to provide seamless investigation workflows.Trigger Integrations
These integrations allow you to invoke IncidentFox:| Integration | Trigger Method | Use Case |
|---|---|---|
| Slack | @mention bot | General investigations, ad-hoc queries |
| GitHub | @mention in PR/issue | CI/CD failures, code-related issues |
| PagerDuty | Webhook on alert | Automatic incident investigation |
| Incident.io | Webhook on incident | Integrated incident response |
Integration Architecture
Quick Setup
1
Choose Your Integrations
Most teams start with Slack for general use, then add GitHub for CI/CD workflows.
2
Install the App
Follow the setup guide for each integration to install the necessary apps/webhooks.
3
Configure Permissions
Grant IncidentFox appropriate read permissions for your channels/repos.
4
Test the Connection
Send a test message or trigger to verify the integration works.
Integration Comparison
| Feature | Slack | GitHub | PagerDuty | Incident.io |
|---|---|---|---|---|
| Manual trigger | Yes | Yes | No | No |
| Auto-trigger on alert | No | No | Yes | Yes |
| Response in same tool | Yes | Yes | Via Slack | Via Slack |
| Rich formatting | Yes | Yes | Yes | Yes |
| Thread support | Yes | Yes | N/A | N/A |
| Requires webhook | No | Yes | Yes | Yes |
Recommended Setup
For General SRE Teams
- Slack - Primary interface for investigations
- PagerDuty - Auto-investigate on alerts
- GitHub - For deployment correlations
For Development Teams
- Slack - Quick queries and debugging
- GitHub - CI/CD failure analysis
- PagerDuty - Production alert context
For Platform Teams
- Slack - General investigations
- Incident.io - Formal incident response
- All data sources - Comprehensive access