# Heroku
[Heroku](https://www.heroku.com/) is a platform as a service (PaaS) that enables developers to build, run and operate applications entirely in the cloud.
Route detailed alerts from Heroku to the right users in Squadcast.
### How to integrate Heroku with Squadcast
### In Squadcast: Using Heroku 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 **Heroku**. Copy the displayed **Webhook URL** to [configure](#in-heroku-set-up-a-webhook-for-squadcast) it within **Heroku.** 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 %}
### In Heroku: Set up a Webhook for Squadcast
**(1)** Navigate to the Dashboard page for your application. In the drop-down menu below, select **More**. You will see an option to **View Webhooks** that will take you to the Webhooks creation and management interface
**(2)** Here, click on **Create Webhook**
**(3)** Provide a suitable **Name** for the Webhook, paste the previously copied **Webhook URL**, select all the checks for which you want to create incidents in Squadcast and click on **Add Webhook**
This completes the configuration of a Webhook in Heroku for Squadcast!
#### Supported Entities and Event Types
The below table indicates the Heroku Entities for which this integration would trigger and resolve incidents in Squadcast. If `Resolve` is mentioned against an Entity, it means the triggered incident in Squadcast will be automatically resolved when Heroku sends a resolve signal for it. For the other Entities, Squadcast users will be notified for the triggered incident. They will have to manually resolve these incidents in Squadcast once the issues are fixed in Heroku.
| Heroku Entities | Squadcast Incident Event Types |
| ---------------- | ------------------------------ |
| addon-attachment | Trigger |
| addon | Trigger |
| app | Trigger |
| build | Trigger, Resolve |
| collaborator | Trigger |
| domain | Trigger |
| dyno | Trigger, Resolve |
| formation | Trigger |
| release | Trigger |
| sni-endpoint | Trigger |
| ssl-endpoint | Trigger |
#### Helpful Links to Heroku's Documentation
**1.** You can find more details about Entities and Event Details [here](https://devcenter.heroku.com/articles/app-webhooks#step-2-determine-which-events-to-subscribe-to)
**2.** You can find more information on setting Webhooks up [here](https://devcenter.heroku.com/articles/app-webhooks).
*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*
---
# 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://support.incidents.cloud.solarwinds.com/integrations/alert-source-integrations-native/heroku.md?ask=
```
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.