Down) and recovery (Up) notifications to Flashduty On-call. Each StatusCake test maps to one Flashduty alert: the alert triggers when the test goes down, repeated down notifications merge into the same alert, and the alert recovers when the test is up again.
In Flashduty On-call
You can get the integration push URL in either of the following ways.
Use a dedicated integration
- In the Flashduty console, go to Channels and open a channel
- Select Configuration → Integrations → Private integration, then click Add an integration
- Select StatusCake and click Save
- Open the new integration card and copy the push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select StatusCake and enter an integration name
- Configure the default route and select a channel. You can add more rules under Routes after creation
- Click Save and copy the generated push URL
Configure StatusCake
1
Create a notification group
- Sign in to StatusCake, go to Alerting → Notification Groups, and click New Notification Group (notification groups are the contact groups of the older interface)
- Enter
Flashdutyas the Group Name - Paste the complete Flashduty push URL into Webhook URL
- Keep Webhook Method at POST (the default)
- Optionally click Test next to Webhook URL to check the URL: Flashduty answers with success and creates no alert
- Save the group
On StatusCake’s Free plan, alerts go to the account email only. Webhook delivery needs a paid plan (Superior or higher; a free trial works).
2
Attach uptime tests
Edit each uptime test you want to connect, select the
Flashduty group under Who to Alert (Contact Groups), and save. One group can serve many tests.3
Verify the lifecycle
Make a test actually go down (for example, point it at an unreachable address for a moment) and confirm that Flashduty receives an active alert. Then restore the target and confirm that the same alert recovers.
Payload fields
StatusCake posts the following fields as an
application/x-www-form-urlencoded form. Flashduty parses them directly; no template is needed.
The alert title is the test name. If the name is empty, Flashduty uses the tested address, then
StatusCake test <TestID>.
Alert Key
Flashduty uses
TestID as the Alert Key. Down, repeated down, and up notifications for the same test carry the same TestID, so they land on the same alert. Two different tests produce different alerts even if they share a name and address. Changing the test name, status code, or tags does not change the Alert Key.
Flashduty returns a parameter error when TestID is missing, because the recovery notification could not otherwise be matched to the original alert.
Status and severity
StatusCake notifications carry no severity, so Flashduty treats every alert as Critical.
Requests with an empty or any other
Status are rejected, so a request whose state cannot be determined never enters the wrong alert lifecycle.
FAQ
Do repeat alerts create more Flashduty alerts?
Do repeat alerts create more Flashduty alerts?
No. When Repeat Alerts is enabled on the notification group, every notification sent while the test stays down carries the same
TestID and merges into the same alert.Can SSL, PageSpeed, or domain checks be connected?
Can SSL, PageSpeed, or domain checks be connected?
This integration is built for the
Down / Up notifications of uptime tests, including Heartbeat tests. Other check types that also post through a notification group are accepted only when the request carries a TestID and Status is Down or Up; otherwise Flashduty returns a parameter error.The notification group test succeeds, but real alerts do not arrive
The notification group test succeeds, but real alerts do not arrive
The notification group test only proves that the URL is reachable. Check that the test is attached to the notification group, that the test is not paused, and that the outage lasts long enough to meet the test’s confirmation setting.
Troubleshooting
- StatusCake fails to deliver: Make sure the Webhook URL is the complete push URL and includes
integration_key - Flashduty returns a parameter error: Make sure Webhook Method is POST and that
TestIDandStatusare not empty - The alert does not recover: Make sure the test is still attached to the same notification group when it recovers; the up notification must carry the same
TestIDas the down notification