> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/about-integrations.md).

# About Integrations

- [Expel Integrations](https://docs.expel.io/connect-your-technology/about-integrations/expel-integrations.md): This page contains a full list of our supported integrations.
- [Why Expel Asks for Console Access](https://docs.expel.io/connect-your-technology/about-integrations/why-expel-asks-for-console-access.md)
- [About SIEM Integrations and Connections](https://docs.expel.io/connect-your-technology/about-integrations/about-siem-integrations-and-connections.md): This topic helps you understand the difference between SIEM integrations and SIEM connections, and how you can leverage each one.
- [MDR SIEM Tiers](https://docs.expel.io/connect-your-technology/about-integrations/tiers-and-support.md): Tiers specify what we can ingest for each integration, whether or not custom rules are leveraged, and which resulting Expel actions are supported.
- [About MDR for Email](https://docs.expel.io/connect-your-technology/about-integrations/about-mdr-for-email.md): MDR for Email provides 24/7 SOC coverage of the alerts generated by your email security tools.
- [Creating Test Alerts](https://docs.expel.io/connect-your-technology/about-integrations/creating-test-alerts.md): After you successfully connect to a cloud environment, you can create a test alert to confirm it is working and learn more about how Expel responds to incidents.
- [Webhooks Setup for Workbench](https://docs.expel.io/connect-your-technology/about-integrations/webhooks-setup-for-workbench.md)
- [Webhook Model Reference](https://docs.expel.io/connect-your-technology/about-integrations/webhook-model-reference.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.expel.io/connect-your-technology/about-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.