User-owned notification bridge

Bring the signal to your channels.

Competitors can offer a built-in alert channel. ResetPulse gives you the same practical reach while keeping the delivery data plane in your own GitHub repository: Telegram, Discord, Slack, or any future webhook target.

ResetPulse sends no channel credential and does not hold a bot token, chat ID, or webhook URL. The workflow fetches and verifies the public packet in your environment.

One workflow, three optional destinations

Copy the multi-channel YAML recipe, add only the secrets for channels you control, and run it once manually. It sends only when a new primary event reaches confirmed and the SHA-256 receipt passes validation; context-only changes do not create duplicate alerts.

Add RESETPULSE_TELEGRAM_BOT_TOKEN and RESETPULSE_TELEGRAM_CHAT_ID. The bot and destination remain yours.

Discord

Add RESETPULSE_DISCORD_WEBHOOK_URL for a channel webhook you own. The workflow posts a compact evidence link.

Slack

Add RESETPULSE_SLACK_WEBHOOK_URL for an incoming webhook in your workspace. Leave it empty if you do not want Slack delivery.

Any webhook

The existing generic recipe remains available for custom automation, incident tools, or self-hosted endpoints.

Why this is different

Built-in channels are convenient, but they make the monitor the owner of delivery state. This bridge keeps the evidence contract public and the notification credentials user-owned. You can inspect the workflow, change the destinations, disable the schedule, or replace the repository without changing the public signal source.

Keep the evidence boundary

The message means “a new verified public ResetPulse signal was observed.” It does not prove that every plan or personal account changed at the same moment. For the source and observation clocks, open the Freshness Lab; for a machine-readable packet, use the Verified Reset Packet.