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

# Types of integrations

ilert integrations connect your tools and workflows for efficient incident management and reliable alerting. They are organized into three categories:

1. **Inbound Integrations**\
   Also called [alert sources](/alerting/configure-alerting/alert-sources.md), they enable you to connect monitoring tools, ticketing systems, or applications to ilert for reliable incident alerting. Use pre-built integrations, email, Event API, SMS, or heartbeat monitoring to create and manage incidents effectively.
2. **CI/CD integrations**\
   [Deployment events](/alerting/deployment-events.md) enrich incidents by bringing deployment activity, such as releases or merges, into your ilert incident management platform.
3. **Outbound Integrations**\
   Known as connectors and [alert actions](https://docs.ilert.com/#connector-and-alert-action-aka-outbound-integration), outbound integrations let you automate incident responses. Update status pages, create tickets in JIRA, or send notifications to Slack to ensure timely and coordinated incident response.

Learn how to configure each type of integration to enhance your incident management operations:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Inbound integrations</td><td><a href="https://docs.ilert.com/alerting/alert-sources">https://docs.ilert.com/alerting/alert-sources</a></td><td><a href="https://docs.ilert.com/alerting/alert-sources">https://docs.ilert.com/alerting/alert-sources</a></td><td><a href="/files/QpcoNTvIWf3UAtKSGb6t">/files/QpcoNTvIWf3UAtKSGb6t</a></td></tr><tr><td>CI/CD pipelines</td><td><a href="https://docs.ilert.com/alerting/deployment-events">https://docs.ilert.com/alerting/deployment-events</a></td><td><a href="https://docs.ilert.com/alerting/deployment-events">https://docs.ilert.com/alerting/deployment-events</a></td><td><a href="/files/V7phvH4zQNsXj2vVvrb2">/files/V7phvH4zQNsXj2vVvrb2</a></td></tr><tr><td>Outbound integrations</td><td><a href="https://docs.ilert.com/#connector-and-alert-action-aka-outbound-integration">https://docs.ilert.com/#connector-and-alert-action-aka-outbound-integration</a></td><td><a href="https://docs.ilert.com/#connector-and-alert-action-aka-outbound-integration">https://docs.ilert.com/#connector-and-alert-action-aka-outbound-integration</a></td><td><a href="/files/t0UVLYoLj9wHQ8tfzVja">/files/t0UVLYoLj9wHQ8tfzVja</a></td></tr></tbody></table>


---

# 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://docs.ilert.com/integrations/types-of-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.