> 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/freshping.md).
# Freshping
[Freshping](https://www.freshworks.com/website-monitoring/) is a simple Uptime and Performance monitoring tool which keeps track of the performance and downtime of websites, APIs, web services, and web applications with real-time alerts.
Route detailed monitoring alerts from Freshping to the right users in Squadcast.
### How to integrate Freshping with Squadcast
### In Squadcast: Using Freshping 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**.
2\. Select **Freshping**. Copy the displayed **Webhook URL** to [configure](#create-a-squadcast-webhook-in-freshping) it within **Freshping.** Finish by clicking **Add Alert Source** -> **Done**.
{% 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 %}
### Create a Squadcast Webhook in Freshping
#### In Freshping: Create a Squadcast Webhook
**(1)** Login to your Freshping web console and navigate to **Settings**
**(2)** Then, select **Integrations**. Scroll down to the **Webhook** section and select **+ Create Integration**
**(3)** Here:
**(a)** Give a meaningful under **Webhook Name**
**(b)** Select the applicable **Event Type** from the drop-down
**(c)** Choose for what **Checks** of yours should Squadcast's Webhook be triggered for
**(d)** Paste the previously copied Squadcast Webhook under **Trigger the webhook**
**(e)** Ensure the **Requires Basic Authentication** checkbox is **unchecked**
**(f)** Next, you can either choose **Simple** or **Advanced** options for the `JSON Encoding`. At the bare minimum, we expect the below information for the integration to work fine:
```json
{
"text": "{text}",
"check_id": "{check_id}",
"check_name": "{check_name}",
"check_url": "{check_url}",
"request_location": "{request_location}",
"request_datetime": "{request_datetime}",
"request_timeout": "{request_timeout}",
"response_state": "{response_state}",
"response_status_code": "{response_status_code}",
"response_time": "{response_time}",
"response_summary": "{response_summary}"
}
```
In addition to this, if you wish to send more data to Squadcast via this Webhook, ensure the data is **valid** `JSON`.
**(g)** Click on **Save**
**(4)** You can verify the creation of your Webhook for Squadcast on the **Integrations** page
**NOTE**: When you click on the **Test** button, Freshping sends out a test alert that would trigger a test incident in Squadcast.
That is it, you are good to go!
Now, whenever Freshping generates an alert, an incident will be triggered for it in Squadcast. Additionally, once the alert that triggered the incident is resolved in Freshping, the corresponding Squadcast incident would get **resolved automatically.**
*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/freshping.md?ask=&goal=
```
`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.