> For the complete documentation index, see [llms.txt](https://help.isdown.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.isdown.app/integrations/how-to-set-up-incident.io-integration.md).

# How to Set Up incident.io Integration

1. Go to your [**incident.io**](https://incident.io) **Account**
2. Select "**Alerts**" in the Sidebar and then the "**Sources**" tab.
3. Click **"Connect an alert source"**
4. Search for "http" and check the option. Choose a name, like "IsDown" and click Continue.

   <figure><img src="/files/IvFYrpswOYBysZAh5l7k" alt=""><figcaption></figcaption></figure>
5. Grab the value from URL and the token after the string "Bearer".
6. Go to the **IsDown account,** in the **"Alerts & Integration"** section.&#x20;
7. Fill the values of Webhook URL with the incident.io URL value, and the Token with the string after "Bearer"

<figure><img src="/files/qxtrka4otLmHYKh0G8Jl" alt=""><figcaption><p>Image 1</p></figcaption></figure>

<figure><img src="/files/8np3TXERLsJLNhbxO6yv" alt=""><figcaption><p>Image 2</p></figcaption></figure>

8. In IsDown, click **Save Changes**. After saved go back to the incident.io section (in IsDown) and click on the "**Send test alert**" button.
9. Go back to incident.io, and configure the fields against the information that goes in the payload that IsDown sends. Click "**Save"** in the end.

IsDown will now opening and closing alerts in incident.io. This will respect the notification settings that you've for each service.

Have questions? We're here to help—contact us via chat or email us at **<support@isdown.app>.**

***

**Related Articles**

* [**How to Set Up Opsgenie Integration**](https://help.isdown.app/integrations/setup-opsgenie)
* [**Set Up Admin SSO**](https://help.isdown.app/accounts/setup-admin-sso)
* [**How to Add a Website Monitor**](https://help.isdown.app/website-monitors/how-to-add-a-website-monitor)


---

# 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://help.isdown.app/integrations/how-to-set-up-incident.io-integration.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.
