Skip to main content
Use a StatusCake notification group (formerly contact group) webhook to send uptime test down (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

  1. In the Flashduty console, go to Channels and open a channel
  2. Select Configuration → Integrations → Private integration, then click Add integration
  3. Select StatusCake and click Save
  4. Open the generated integration card and copy the Push URL

​
Use a shared integration

  1. In the Flashduty console, go to Integration Center → Alert Events
  2. Select StatusCake and enter an integration name
  3. Configure the default route and select a channel. You can add more rules under Routing after creation
  4. Click Save and copy the generated Push URL

​
Configure StatusCake

1

Create a notification group in StatusCake

Where: StatusCake › AlertingOn the Alerting page, click the new-group button (New Contact Group). Notification groups are called Notification Groups in the current interface and Contact Groups in the older one.Save the group. The Test button next to Webhook URL only confirms that the URL is reachable: Flashduty answers with success and creates no alert, so it cannot verify the alert lifecycle.
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 the group to uptime tests in StatusCake

Where: StatusCake › Monitors › All MonitorsEdit each uptime test you want to connect, fill in the field below, and save. One group can serve many tests.StatusCake has no separate recovery switch: when a test recovers it sends an Up notification automatically and Flashduty closes the alert. Just keep the group attached to the test.
3

Verify with a real outage and recovery

Where: StatusCake › Monitors › All MonitorsMake a test that has the group attached 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. Back in Flashduty, the integration shows Latest event time, which means the setup works.
Webhook Method must be POST. With GET, StatusCake only requests the URL without a request body, so Flashduty cannot read the test ID or status.

​
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

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.
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 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 TestID and Status are 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 TestID as the down notification
For field details, see the StatusCake documentation How To Use The Web Hook URL.