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

# Integration Providers

IT-Conductor Alerts can be configured to flow to an external system such as Service Desk applications as Incidents or Chat/Collaboration services as message posts.

IT-Conductor currently supports the following out-of-the-box integrations:

* [Derdack EA Integration](/user-guide/notifications/integration-providers/derdack-ea.md)
* [ilert Integration](/user-guide/notifications/integration-providers/ilert.md)
* [Jira Service Desk Integration](/user-guide/notifications/integration-providers/jira-service-desk.md)
* [Microsoft Teams Integration](/user-guide/notifications/integration-providers/microsoft-teams.md)
* [PagerDuty Integration](/user-guide/notifications/integration-providers/pagerduty.md)
* [Slack Integration](/user-guide/notifications/integration-providers/slack.md)

{% hint style="info" %}
**Note:** We also support custom integrations by request. Please contact the [IT-Conductor Support Team](/references/support.md) for assistance.
{% endhint %}

These integrations can now be used as subscription subscribers. See [Creating Notification Subscriptions](/user-guide/notifications/subscriptions.md).

{% hint style="info" %}
**Note:** The mappings between IT-Conductor alert attributes and target integration system item attributes are preconfigured but can be customized based on specific requirements. Please contact the [IT-Conductor Support Team](/references/support.md) for assistance.
{% endhint %}


---

# 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.itconductor.com/user-guide/notifications/integration-providers.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.