Skip to main content
Connect StatusCake to Rootly using the Generic Webhook Alert Source. StatusCake sends form-encoded webhook data; Rootly uses the decoded fields to create, route, and resolve alerts.

​
Connect StatusCake

Create the Rootly Source

Follow the Generic Webhook installation instructions to create and name your source.Copy its base webhook URL and add the source’s secret query parameter as described in Authentication. Configure routing in Rootly using the instructions below.

Configure the StatusCake Contact Group

Paste the complete Rootly URL into a StatusCake contact group’s webhook configuration and choose HTTP POST.Follow StatusCake’s contact group instructions to associate the group with the uptime checks you want to send to Rootly. For supported encoding and shared troubleshooting, see Generic Webhook payload formats.

​
Map StatusCake Fields

Use the fields in the actual StatusCake webhook payload when configuring your source’s field mappings. StatusCake’s webhook reference describes these fields: For the external identifier, choose a value that is unique per check and stays the same between Down and Up events. Use URL only when each check has a unique URL; checks monitoring the same URL need another stable identifier from their payload. Confirm the extracted values in the payload preview. For Liquid mappings, see Alert Fields.

​
Route and Resolve Alerts

Create an Alert Route for this source. Add a rule that matches $.Status equal to Down, with your intended team, service, or escalation policy as the destination. Rootly selects the destination from this rule, so the StatusCake payload does not need Rootly target IDs. Add check-specific conditions and destinations when checks should notify different responders. Enable deduplication by unique identifier using the stable check identifier. Configure auto-resolution with the same identifier and the recovery state Up. Send recovery events to the same webhook URL.

​
Test the Connection

Test the following sequence from StatusCake:
  • Send a Down event and confirm that Rootly creates an alert and notifies the intended destination.
  • Send another Down event for the same check and confirm that deduplication uses the existing alert.
  • Send an Up event and confirm that it resolves that alert.
  • Repeat with a second check to confirm that its alerts stay separate.