Squadcast Docs
Visit Build Integrations on GitHub
Set theme to dark (⇧+D)

Build Alert Sources

Squadcast supports over 100+ integrations with a range of observability tools in the market today as alert sources.

Squadcast now offers a platform for its users & partners to build their integrations with the tools of their choice and route alerts into the platform via Webhooks.

Integrations are built using Webhooks. These integrations can support both triggering and automatic resolution of alerts in Squadcast when the alerts in the observability tool get resolved and send signals via the configured Webhooks.

Users can build an integration by creating a PR to this repository by adding a folder for this integration, along with the manifest file, sample payloads, docs and images.

While we encourage users to build custom integrations for the observability tools of their choice based on their requirement, if the observability tool for which users are looking to build an integration supports customisable payload structures, we recommend users to simply use our Incident API Webhook to route events directly into Squadcast.

If the observability tool for which users are looking to build an integration does not support Webhooks, users can make use of our Email integration to route events into Squadcast.

Github - https://github.com/SquadcastHub/Alert-Source-Integration

Folder Structure

For every alert source integration that is built , there needs to be a branch for it by it’s name. This branch will contain folders with information as indicated below:

Folder name

The folder name should be same as the name of the alert source.


A YAML file manifest.yaml (formatted using Markdown) with the logic for the alert source integration to work.

Naming convention: manifest.yaml

Refer the How to write manifest file? for more details.

payload (sub-folder)

A sub-folder called payload will contain the JSON files that have the payloads sent from the observability platform. The alert source integration can have 1 or more of the following:

  • Trigger payload(s)
  • Resolve payload(s)
  • Test payload(s)

Naming convention: <alert-source-name>-<trigger/resolve/critical/warning/test>-payload.json


This Markdown file containing the steps to configure the alert source integration. This will be used as the documentation guide for other users to configure the alert source integration. The file will contain two sections:

  • Steps that need to be performed by a user in Squadcast
  • Steps that need to be performed by a user in the observability platform

Naming convention: documentation.md


images (sub-folder)

This folder will contain images that need to be added into the documentation to help a user visualise the process of configuring an alert source integration with ease. This could also include logos of the tool, etc.


An optional json file with the author information and contact details in the below format.

  author-type: "Partner|Squadcast|Community",
  name: "Acme Inc.|Squadcast, Inc"
  • Partner: If the alertsource partner themself is building the integration with us
  • Squadcast: When Squadcast builds the integration with the tool
  • Community: Anyone else voluntarily building the integration between Squadcast and the tool

Naming convention: author.json

General Process

  1. Capture the payloads being sent for different events from the observability tool by setting up Webhooks in sites like webhook.site

  2. Add the payloads in JSON to the Payloads folder in the branch. Payloads should contain valid JSON content. Validation can be performed by using sites like JSONLint. This folder would contain one or more of the following:

    • Trigger payload(s) - Payloads that create/trigger an incident in Squadcast to alert/notify users, there could be multiple types of trigger payloads like Critical, error etc, everything should be captured and named appropriately.
    • Resolve payload(s) - Payloads that resolve an existing incident in Squadcast when the corresponding event in the observability tool is resolved. The presence/absence of such a payload determines if the integration being built would support auto-resolution of incidents in Squadcast or not.
    • Test payload(s) - Payloads for test events sent by the observability tool. Some tools support this by having a “Test” option, whereas some do not. If the tool supports it, then this payload needs to be present.
  3. Start developing the code for the integration that would be contained in the “Manifest” as a YAML file

    Refer the below sections for more information:

    How ro write manifest file?

    Available Template functions for use in manifest

  4. Document the integration.

    For this:

    • Follow the pattern used for existing integration documentation. The structure is as follows:
      • Steps that need to be performed by a user in Squadcast
      • Steps that need to be performed by a user in the observability platform
    • Screenshots need to be captured for steps where applicable and added to the right folder
    • A link to the official website of the observability tool also needs to be provided
  5. Create a PR and mark the options as applicable in the checklist to make the review process easier and quicker.

  6. The team at Squadcast will review the PR and contact the contributor in case of further queries and work towards getting the integration into the platform as quickly as possible and make it functional for consumption.