CLAUDE NOTIFICATIONS
Claude Notifications
Страницы · Claude Notifications

/notify-channel — build a custom channel

Build a custom notification channel handler — Telegram, Microsoft Teams, Pushbullet, SMS via a non-Twilio provider, internal company chat, anything. Use when the user wants notifications somewhere the built-in channels don't support, or wants to fork an existing channel for a different API shape.

The dispatcher (scripts/notify.sh) auto-discovers channels in two locations:

  1. ${CLAUDE_PLUGIN_ROOT}/scripts/channels/<name>.sh — shipped with the plugin
  2. ~/.claude-notifications/channels/<name>.sh — user-installed custom channels

Drop a script in #2 and it works. No registration step.

Template

bash

Rules to follow

  1. Never block Claude Code. Time-bound every network call; non-zero exits are swallowed by the dispatcher but slow handlers will block until the 5s timeout.
  2. Log instead of printing. cn_log "..." writes to ~/.claude-notifications/logs/notify.log. Stdout/stderr go to the same log file via the dispatcher.
  3. Default-off behavior on missing config. If credentials are absent, log and exit 0 — don't error.
  4. Respect level. CN_LEVEL is info|warn|error|success. Map it to whatever color/severity the target API uses.
  5. Make enabled: false an automatic skip. The dispatcher already does this — the channel won't be invoked unless channels.<name>.enabled is true.

Common targets — where to point curl

ServiceEndpointAuth
Telegramhttps://api.telegram.org/bot<TOKEN>/sendMessagebot token in URL
MS TeamsIncoming Webhook URL from connectornone (URL is secret)
Pushbullethttps://api.pushbullet.com/v2/pushesAccess-Token header
MattermostIncoming Webhook URLnone
ntfy.sh (self)https://your-ntfy/<topic>optional bearer
Twitter/X DMOAuth 1.0a — use a small Python helper, not bashOAuth tokens

After writing

  1. chmod +x ~/.claude-notifications/channels/<name>.sh
  2. Add the channel block to user config:
    bash
  3. Test with the dispatcher:
    bash
  4. Confirm with one line. Don't paste the script back at the user — they wrote it (or you wrote it for them and they can read it).