> For the complete documentation index, see [llms.txt](https://support.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://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/nodeping.md).

# NodePing

[<mark style="color:blue;">NodePing</mark>](https://nodeping.com/) provides uptime monitoring for websites and servers.

Route detailed alerts from NodePing to the right users in Squadcast.

### How to integrate NodePing with Squadcast

#### In Squadcast: Using NodePing as an Alert Source

1. Navigate to **Services** -> **Service Overview** -> select or search for your Service. Expand the accordion -> In the Alert Sources section, click **Add**.

![](/files/ej4AI9zpOyFu5NZJCbwC)

2\. Select **NodePing.** Copy the displayed **Webhook URL** to [configure](#in-nodeping-create-a-squadcast-webhook-alert) it within **NodePing**. Finish by clicking **Add Alert Source** -> **Done.**

![](/files/g5WL4d2pirlNCQNVW5Rs)

{% hint style="warning" %}
**Important:**

When an alert source turns Active, it’ll show up under Configured Alert Sources, you can either generate a test alert from the integration or wait for a real-time alert to be generated by the Alert Source. An Alert Source is active if there is a recorded incident via that Alert Source for the Service.
{% endhint %}

#### In NodePing: Create a Squadcast webhook alert

**(1)** In the app, click on **Checks & Contacts > Contacts > Add new contact**

![](/files/EqL74uytHTOSJTwLoGeN)

**(2)** Provide any suitable Name, select **Webhook** option in the drop-down, change method name from **GET** to **POST**. Paste the previously copied **Webhook URL** in the **URL field**

![](/files/GzaJIVEceZQnR7m3mCbS)

**(3)** Click on **Body > RAW** and copy the below payload and paste this in the **JSON** section and click on **Save**

```
{
	"id" : "{_id}",
	"label" : "{label}",
	"event" : "{event}",
	"uuid" : "{uuid}",
	"ci" : "{ci}",
	"t" : "{type}",
	"tg" : "{target}",
	"i" : "{interval}",
	"s" : "{start}",
	"e" : "{end}",
	"rt" : "{runtime}",
	"sc" : "{statuscode}",
	"su" : "{su}",
	"m" : "{message}"
}
```

![](/files/EHoFOl5LNfPlOQLZComr)

**(4)** Click on **Checks & Contacts > Checks** and edit the check. Scroll to the **Notify** section and select the Contact created for Sqaudcast in the drop-down and click on **Save**

![](/files/aXnNmDTuGuwEh5cZjY5L)

You can find more information on setting this up [here](https://nodeping.com/nodepingnotifications.html#webhooks).

That is it, you are now good to go! Whenever an alert is generated in NodePing, an incident will be created in Squadcast. When the alert is resolved in NodePing, the corresponding incident will automatically get resolved in Squadcast as well.

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*


---

# 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://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/nodeping.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.
