> For the complete documentation index, see [llms.txt](https://developers.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.incidents.cloud.solarwinds.com/integration-and-extensibility/build-integrations/_index.md).

# Build Integrations

There are 3 types of integrations available in Squadcast.

### Alert Sources

We integrate with various monitoring, observability, log management & error tracking tools and we call them as Alert sources.

All these alert sources uses webhooks as the core mechanism to send data to Squadcast and you can [contact us](mailto:support@squadcast.com) for more details about building this type of integrations.

### Webhook connectors

Webhook connectors are proxy scripts which receives data from [Squadcast outgoing webhooks](https://github.com/bhattu-gauravv/developers.squadcast.com/blob/main/outgoing-webhooks/README.md) and transforms the payload to the required format of the 3rd party system which we are integrating with.

For more information about creating webhook connectors, please refer the [Webhook connector](/integration-and-extensibility/webhooks/outgoing-webhooks/_index/webhook-connectors.md) documentation.

### Extensions

Extensions are advanced type of integration which are built-in within Squadcast to perform various actions based on the extension type.

**Currently available extensions**

#### ChatOps

* [Slack](https://support.squadcast.com/docs/slack)
* [Microsoft Teams](https://support.squadcast.com/docs/msteams)
* [Google Hangouts](https://support.squadcast.com/docs/hangouts)

#### Ticketing

* [Jira Server](https://support.squadcast.com/docs/jira-server-on-premise)
* [Jira Cloud](https://support.squadcast.com/docs/jira-cloud)

#### CI/CD

* [CircleCI](https://support.squadcast.com/docs/circleci-integration)

If you would like to build an extension, please [contact us](mailto:support@squadcast.com).


---

# 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://developers.incidents.cloud.solarwinds.com/integration-and-extensibility/build-integrations/_index.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.