> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/settings/integrations.md).

# Integrations

Connect Slack, Teams, documents, monitoring, and ticketing — without changing how you work today.

**Settings → Integrations** is where Administrators connect the tools your team already uses. Incident Lake then brings those conversations and records onto the incident.

{% hint style="warning" %}
Connect a **shared organization account**, not a personal one. Everyone in the workspace will rely on that connection.
{% endhint %}

## Communication

| Integration         | What your team gets                                                                                |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| **Slack**           | Create incidents from a thread, receive updates, and (when users are linked) update tasks in Slack |
| **Microsoft Teams** | The same idea in Teams: create incidents and receive notifications from the team conversation      |

After Slack or Teams is connected, invite the Incident Lake bot to the channels that should participate, then link members to their chat users.

## Documents and knowledge sources

| Integration      | What your team gets                                                                               |
| ---------------- | ------------------------------------------------------------------------------------------------- |
| **Google Drive** | Search and attach files from folders you allow. Add only the folders the incident team should see |
| **Notion**       | Search pages and databases your workspace has connected                                           |

## Monitoring and status

| Integration    | What your team gets                                                          |
| -------------- | ---------------------------------------------------------------------------- |
| **Datadog**    | Alerts and related context can help open or enrich an incident               |
| **Zabbix**     | Related trigger firings can be grouped into one incident and posted to Slack |
| **Instana**    | Related events can be grouped into one incident and posted to Slack          |
| **Statuspage** | Publish a reviewed update to your public status page                         |

The **Incident Response Agent** can open a Slack prompt when an alert arrives, then help with the first triage after someone confirms it. A person always accepts or dismisses the alert.

## Ticketing

| Integration | What your team gets                      |
| ----------- | ---------------------------------------- |
| **Jira**    | Link and follow issues from the incident |
| **Backlog** | Link and follow issues from the incident |

## If a connection is missing

Some integrations are part of an add-on. If you do not see a product you expected, ask your Incident Lake contact or write to <support@sigq.co.jp>.

To reconnect Slack, Teams, or Drive with a different workspace or account, disconnect first, then connect again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidentlake.com/settings/integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.