> 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/checkly.md).
# Checkly Integration
Connect Checkly uptime and API monitoring to ilert to convert failures into real‑time alerts, ensuring SLA visibility and fast recovery.
By integrating [Checkly](https://www.checklyhq.com/) with ilert, synthetic monitoring failures – such as downtime or API errors – are instantly transformed into actionable alerts. Teams receive real-time notifications, escalation sequences are triggered automatically, and SLA compliance is kept in focus for faster service recovery.
## In ilert: Create a Checkly alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Checkly**, 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**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
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 Checkly: Add an ilert alerting channel
1. Go to **Alerts** and click on **Add more channels**.
2. Browse to ilert in the list of channels and click on **Add channel**
3. Give the alert channel a name (e.g. ilert) and paste the **Checkly URL** from above in the URL field. Optionally change the notification events. Recovery notifications will resolve existing alerts in ilert that were created from checkly. **Do not edit the payload**.
4. Click **Save ilert webhook**.
## FAQ
#### **Will alerts in ilert be resolved automatically?**
Yes, as soon as a check in checkly recovers, the associated alert in ilert will be resolved automatically. Make sure that the option **Send alert notifications when a check recovers** is enabled in the alert channel settings in Checkly.
#### **Can I link Checkly to multiple alert sources in ilert?**
Yes, create an **alert channel** per alert source in Checkly.
#### **Can I also receive SSL certificate expiration alerts in ilert**
Yes. Simply enable the **Send alert notifications when an SSL certificate is due to expire in x days** in the alert channel settings in Checkly.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ilert.com/integrations/inbound-integrations/checkly.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
