PingChange LogoPingChange
Sign inStart monitoring

Notification channels

Connect email, Slack, Telegram, and webhooks so PingChange can deliver change alerts to your team.

Notification channels are reusable destinations. You create them once under Dashboard → Channels, then pick which ones each monitor should use in the monitor wizard or monitor settings.

After saving, use any test or send sample action the app offers so you know messages arrive before real changes fire.

Email

Good for: individuals and small groups, legal or exec forwarding, anywhere you want a normal inbox message.

Setup

  1. Go to Dashboard → Channels → add or edit a channel → choose Email.
  2. Fill in Channel name (how it appears in PingChange).
  3. Recipients — one or more addresses, comma-separated.
  4. Subject prefix — optional tag like [PingChange] so filters catch alerts.
  5. Send frequency — choose how often alerts are delivered (see below).
  6. Save.

Send frequency

OptionDescriptionPlan
On monitor check (immediate)An email is sent every time a change is detected — same behaviour as before.Paid plans only
Once a dayChanges are accumulated and sent as a single digest email at the configured UTC hour.All plans
WeeklyChanges are accumulated and sent once per week on the configured day and hour (UTC).All plans

For daily and weekly frequencies you can set:

  • Digest hour — the UTC hour (0–23) at which the digest is sent (default: 9 AM UTC).
  • Digest day of week — for weekly only, the day the digest is sent (0 = Sunday … 6 = Saturday, default: Monday).

The digest email lists every change that occurred since the previous send: monitor name, detection time, summary, keywords, and a link to the full diff in the dashboard.

In alerts you typically see monitor name, URL, a short change summary, a link back to the diff, and sometimes a screenshot when one was captured.

Slack

Available on paid plans (check your subscription for Slack notifications).

Good for: team rooms, on-call visibility, threads with context.

Setup

  1. In Slack, create an Incoming Webhook for the channel you want (Slack admin may need to enable this).
  2. In PingChange: Dashboard → Channels → Slack.
  3. Channel name — label for you (for example #releases).
  4. Webhook URL — paste the URL Slack gave you.
  5. Save, then test from the channels list if available.

In alerts Slack shows a compact card: monitor, change summary, link to open the full comparison, and optional image when a screenshot exists.

Telegram

Good for: mobile-first teams, small groups via a bot.

Setup

  1. Talk to BotFather in Telegram to create a bot and copy the bot token.
  2. Decide the chat or channel ID the bot should post to (group, channel, or direct chat).
  3. In PingChange: Dashboard → Channels → Telegram.
  4. Channel name — label inside PingChange.
  5. Bot token and Chat ID — paste from Telegram.
  6. Save and test.

In alerts Telegram receives a plain text message with the key details and a link to the dashboard diff.

Webhook (custom HTTPS)

Available on higher paid plans (check your subscription for webhook notifications).

Good for: internal services, custom routers, or bridging to tools without a native integration.

Webhook delivery is powered by Svix, which provides automatic retries, signed payloads, and a delivery log you can inspect in your workspace.

Setup

  1. Prepare an HTTPS endpoint that accepts POST requests.
  2. In PingChange: Dashboard → Channels → Webhook.
  3. Channel name — label for you.
  4. Endpoint URL — your HTTPS URL.
  5. Secret (HMAC) — optional shared secret if you verify Svix signatures on your server.
  6. Throttle rate — optional maximum number of events per second Svix will deliver (1–1000). Leave blank for no limit.
  7. Save and test.

Svix delivery

When a change is detected PingChange publishes an event to Svix, which then delivers the POST to your endpoint URL with the following HTTP headers:

HeaderDescription
svix-idUnique message ID (idempotency key)
svix-timestampUnix timestamp of the send attempt
svix-signatureHMAC-SHA256 signature you can verify

Payload — Your server receives a structured JSON body with the change summary, metadata (monitor name, URL, timestamps), links, and optional screenshot URL. Build your handler to read those fields and forward them as you like.

Retries — Svix automatically retries failed deliveries with exponential back-off.

Throttle rate — Set a per-endpoint rate limit if your server needs to cap ingestion speed.

Linking channels to monitors

When you create a monitor, select the channels that should receive its alerts. You can also update linked channels later from the monitor's settings or channels tab.