Send UptimeFlare downtime and recovery alerts to Signalgrid using webhooks
UptimeFlare is a serverless uptime monitoring and status page project built around Cloudflare Workers. Its notification system supports custom webhooks, which makes it easy to forward downtime alerts, recovery notices, and SSL warnings to Signalgrid.
The simplest setup is to configure a Signalgrid webhook inside uptime.config.ts so monitor events appear immediately on your phone.
Prerequisites
- A working UptimeFlare deployment with notifications enabled
- A Signalgrid account
- Your Signalgrid
client_key - A Signalgrid channel token
- Outbound HTTPS access from UptimeFlare to
https://api.signalgrid.co
Configuration Example
This version sends regular Signalgrid notifications and uses $MSG as the body so UptimeFlare inserts its human-readable event text.
TypeScript
webhook: {
url: 'https://api.signalgrid.co/v1/push',
payloadType: 'x-www-form-urlencoded',
payload: {
client_key: 'YOUR_CLIENT_KEY',
channel: 'YOUR_CHANNEL_TOKEN',
title: 'UptimeFlare Notification',
body: '$MSG',
type: 'INFO',
},
},
Critical Configuration Example
Use the critical variant only for the alerts that should bypass quiet mode and Do Not Disturb on supported devices.
TypeScript
webhook: {
url: 'https://api.signalgrid.co/v1/push',
payloadType: 'x-www-form-urlencoded',
payload: {
client_key: 'YOUR_CLIENT_KEY',
channel: 'YOUR_CHANNEL_TOKEN',
title: 'UptimeFlare Critical Alert',
body: '$MSG',
type: 'CRIT',
critical: 'true',
},
},
Parameters
Field
Description
urlSignalgrid Push API endpoint
payloadTypeMust be
x-www-form-urlencoded so UptimeFlare sends a standard form bodyclient_keyYour Signalgrid client key used to authenticate the request
channelThe Signalgrid channel token that should receive the alert
titleA fixed notification title shown on the device
bodyThe notification body. Use
$MSG so UptimeFlare inserts the event texttypeSets the Signalgrid notification type. Since the webhook configuration uses a fixed value, the same type is used for both downtime and recovery notifications
Manual Testing
Before you wait for a real outage, first verify that your Signalgrid credentials and target channel work with a direct API request:
Bash
curl -X POST https://api.signalgrid.co/v1/push \
-d "client_key=YOUR_CLIENT_KEY" \
-d "channel=YOUR_CHANNEL_TOKEN" \
-d "title=Signalgrid test" \
-d "body=Direct API test from the UptimeFlare integration guide" \
-d "type=INFO"
Once that arrives on your device, save the UptimeFlare webhook configuration, redeploy your worker if needed, and wait for the next monitor event or recovery message.
Troubleshooting
Issue
What to check
No Signalgrid notification arrives
Verify the
client_key, the channel token, and that UptimeFlare can reach https://api.signalgrid.co/v1/pushThe webhook runs but Signalgrid rejects it
Make sure
payloadType is x-www-form-urlencoded and that the payload field names match the Signalgrid API exactlyThe message arrives without useful text
Check that the webhook body uses
$MSG instead of a static placeholder or an unsupported variable