INTEGRATIONS
Keep your stack. Give the incident one place to live.
Most incidents touch a monitoring tool, a chat channel, a ticket queue and some record of what runs where. Incident Lake connects to the tools you already run instead of asking you to replace them, and pulls alerts, the live response, follow-up tasks and the final record into a single flow. Below is everything it connects to today, with a plain note on whether each connection only reads or can also write.
How reads and writes work
Connections to monitoring, code and documentation tools are read-only. Task sync with Jira, Backlog and ServiceNow becomes two-way (issue creation and status transitions) only after an admin turns it on. No integration sets severity or closes an incident; a person always makes that call.
Chat
Slack
Joins the incident thread and starts on an “@Incident Lake go” mention. Works across multiple workspaces.
Microsoft Teams
Joins Teams threads and runs the same step-by-step response it does in Slack.
Monitoring
Datadog
Opens incidents from monitor alerts; the agent looks at monitors, logs and traces while investigating.
Sentry
Opens incidents from alerts and pulls in error details while investigating.
Grafana
Opens incidents from alert webhooks and refers to dashboards during investigation.
Zabbix
Opens incidents from triggers and folds related triggers into a single incident.
Instana
Opens incidents from alerts and pulls in related context while investigating.
Rollbar
Opens incidents from alerts and pulls in error details while investigating.
Outlook (alert mailbox)
Ingests an alert mailbox to open incidents and keeps replies in sync.
Code, ITSM and tasks
GitHub
Brings in changes and releases so you can see what shifted right before things broke.
ServiceNow
Search and link incident, problem and change records; task sync; CMDB sync.
Jira
Turns response tasks into issues and keeps status aligned. Jira URLs are linked automatically.
Backlog
Turns response tasks into Backlog issues and keeps status aligned. Backlog URLs are linked automatically.
Docs and CMDB
Notion
Reads runbooks and other pages when investigating or drafting the record.
Google Drive
Reads runbooks and other files when investigating or drafting the record.
NetBox
Syncs infrastructure data into the built-in CMDB to power the service graph and blast-radius view.
Everything else
Statuspage
Connects to your status page so stakeholders hear what is going on.
Meeting bot
Joins Zoom, Google Meet or Teams calls, transcribes them and posts a summary to the incident notes.
Public API
Lets your own systems work with Incident Lake data.
MCP
Incident Lake runs a remote MCP server with OAuth, and the chat agent can use MCP tools.
Connect what you already run. Start free.
There's a free plan. Hook up one chat tool and one monitoring source and walk through a real alert end to end.