We added webhook notifications to QuietPulse

Small but important QuietPulse update today: we added webhook notifications.

Until now, QuietPulse focused on direct alerts through Telegram. That works well for personal monitoring, but webhooks make the product much more flexible for real workflows.

Now users can:

• send a test webhook directly from the dashboard
• receive job.missed events when a heartbeat goes missing
• add an optional signing secret
• verify requests using signature headers instead of exposing the secret itself

I also wrote a practical guide for the feature, so it works both as an announcement and as product documentation:
https://quietpulse.xyz/blog/webhook-notifications-in-quietpulse

This matters because webhooks make QuietPulse easier to integrate with:

• internal tools
• automation platforms like n8n / Make / Zapier
• custom alert routing into Slack, Discord, or anywhere else

One nice side effect: this also pushed the product architecture forward a bit, because notifications are no longer tied only to Telegram internally.

Would love feedback from people who already use webhooks heavily:

• what payload details matter most to you?
• do you prefer generic webhooks first, or provider-specific integrations like Slack/Discord next?