// integrations / checkly

Checkly → your status page

Last updated: September 2026

Checkly runs your API and browser checks; GreenPing turns their results into customer communication. Wired together via webhook, a failing check updates your public status page, opens an incident, and notifies subscribers — and a passing run resolves everything again.

GreenPing reads Checkly's webhook payload natively (the check_result object with its hasFailures flag), so there's no transformation layer to build or maintain.

Setup — GreenPing side (2 minutes)

Create a free page (or open yours), then go to Webhooks → Add Webhook.
Choose Checkly as the source and pick the component this monitor watches.
Copy the generated webhook URL — it's unique and acts as the secret.

Setup — Checkly side

In Checkly, open Alerts → Alert Channels and add a Webhook channel.
Paste your GreenPing webhook URL and keep the method as POST with a JSON body.
Subscribe the checks (or check groups) that should drive your status page to this channel.
Optionally limit alerts to failures and recoveries — the two events GreenPing acts on.

What travels over the wire

Checkly's webhook includes a check_result object; GreenPing keys on hasFailures — true opens an incident, false resolves it:

{
  "check_result": {
    "name": "Checkout API",
    "hasFailures": true
  }
}

Down event → component flips, incident auto-opens, subscribers emailed
Recovery event → incident auto-resolves, component restored, all-clear emailed
Every incident appears on your public page with a timestamped timeline

Common questions

Which Checkly plan do I need?

Webhook alert channels are part of Checkly's core alerting and available broadly, including on their free developer tier — verify against their current plans page, as vendors move features between tiers.

Can browser checks and API checks both drive the page?

Yes — any check subscribed to the webhook alert channel triggers the same flow: failure opens the incident and flips the component; recovery resolves it.

What shows up on my public status page?

The affected component's status changes, and an incident appears with a timestamped 'Investigating' update. Visitors see the incident timeline; subscribers get an email at open and at resolution.

See the loop live on our own page — status.greenping.live runs on this exact integration.

Start free