# Nodejs connectors

GitHub - <https://github.com/SquadcastHub/Squadcast-Webhook-Connectors>

The following connectors are currently available:

### ChatOps

[**Slack**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#slack)

Use this to notify your Slack channels about Squadcast Incident related updates, supports multiple channels. Alternatively, you can use our Slack extension as well.

[**Discord**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#discord)

Use this to notify your Discord channels about Squadcast Incident related updates, supports multiple channels.

[**Trello**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#trello)

Use this to create new Trello cards for Squadcast incidents.

[**Telegram**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#telegram)

Use this to get notified of Incidents via Telegram.

### Email & Ticketing

[**Email (SMTP)**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#email)

Use this to send Incident notifications via email, you can customize the script to change the content of the email. Supports multiple email providers.

[**Linear**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#linear)

Use this to create issues in Linear.

[**ClickUp**](https://github.com/SquadcastHub/Squadcast-Webhook-Connectors#click-up)

Use this to create Tasks in ClickUp.


---

# Agent Instructions: 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:

```
GET https://developers.incidents.cloud.solarwinds.com/integration-and-extensibility/webhooks/outgoing-webhooks/_index/webhook-connectors/nodejs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.