> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/statushub.md).

# StatusHub Integration

Connect Statushub incidents to ilert to notify responders about major incidents and coordinate statuses with stakeholders efficiently.

[StatusHub](https://statushub.com/) is a tool for efficient and flexible communication during incidents and maintenance events. By integrating Statushub with ilert, major incident declarations trigger alert notifications directly to on-call teams. This integration helps ensure rapid response coordination and maintains transparent communication with stakeholders throughout the incident lifecycle.

## In ilert: Create a StatusHub alert source

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **StatusHub**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

## In Statushub

1. Navigate to StatusHub Dashboard or go to your StatusHub Page (If you navigate to StatusHub Page, skip to step 2)

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH55jhD-BCk7-8oQUM%2Fstatushub-statuspageadmin.png?alt=media\&token=1bbb134e-c6ce-43fb-b8ea-260f5d12fd7f)

2. On your StatusHub Page, click on **Subscribe** on the top right

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH5I27p4oQ8vsATpIj%2Fstatushub-statuspage.png?alt=media\&token=f31ceb50-9a09-4b80-bbd7-2fe5d64968d4)

3. Click **Webhook** on the Subscribe Page

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH5O1R9NYBdD1sYhou%2Fstatushub-subscribe.png?alt=media\&token=df363f0c-42a6-4d51-9d8f-c0d3319bec03)

4. Use the **StatusHub URL** that you generated in ilert and paste it in the URL field, and make sure the Content Type is **JSON**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH5RwW8gyM-W9q0r83%2Fstatushub-subscribewebhook.png?alt=media\&token=cbe975ce-6a3e-45cf-95f5-8bbe0f66a15c)

5. On the Customization you can leave it as it is and click **Save**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH5VI1b0jGm1QSV0di%2Fstatushub-customization.png?alt=media\&token=92d0cc4e-7cfd-4bc5-ac8f-609982faf7c5)

6. To trigger the Incident in ilert, just create an Incident from StatusHub Dashboard

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MlH30rGOzdx_o5rO21i%2F-MlH5YL-PN9li6rjRkvC%2Fstatushub-incident.png?alt=media\&token=4709bdd1-8fcb-487f-9b68-266b7063e275)

7. The Incident will be created in ilert automatically upon creating an Incident in StatusHub


---

# 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://docs.ilert.com/integrations/inbound-integrations/statushub.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.
