peepshow/ sinks/ apprise

Reel #73 Notification fan-out

peepshow sink / apprise

AppriseFan out to 80+ notification services via an Apprise API instance.

One sink, every notification channel. Apprise normalises Slack, Discord, Telegram, email, SMS, ntfy, Pushover, and dozens more.

drop · process · apprise

What it does

[Apprise](https://github.com/caronc/apprise) is the lingua franca of push notifications — one tiny URL syntax that targets 80+ services (Slack, Discord, Telegram, Matrix, email, SMS, Pushover, Pushbullet, ntfy, Gotify, Mailgun, MS Teams, …). The companion [Apprise API](https://github.com/caronc/apprise-api) exposes that fan-out as an HTTP endpoint. This sink posts every peepshow run to `/notify` with form-encoded `body`/`title`/`urls`, or to `/notify/<configId>` with a stateful `tag` when you've pre-registered a config server-side. Use it as a single connector that pipes peepshow runs to whatever combination of services your team uses.

When to reach for it

  • Replace 5+ individual sinks with one — Apprise already speaks all of them
  • Centralise notification routing in a self-hosted Apprise API so peepshow stays config-light
  • Mix-and-match — fire to email + Slack + Telegram in a single POST with one stateless URL list

Install

npm i -g peepshow
# Run the Apprise API (Docker):
# docker run -p 8000:8000 caronc/apprise:latest

Use it

APPRISE_BASE_URL="http://localhost:8000" \
APPRISE_URLS="slack://TOKEN/CHANNEL,mailto://user:pass@host" \
peepshow ./clip.mp4 --sink apprise

# Stateful — re-use a saved config on the server:
APPRISE_BASE_URL="http://localhost:8000" \
APPRISE_URLS="tag:home@peepshow" \
peepshow ./clip.mp4 --sink apprise

Make it automatic

Register the sink once — every run fires it afterward. Scope by --when so it only runs for matching videos.

peepshow sinks add apprise
peepshow sinks add apprise --when extension=mp4,mov
peepshow sinks add apprise --when path=/Volumes/Work/

Configuration

  • APPRISE_BASE_URL Base URL of the Apprise API instance (e.g. `http://localhost:8000`). required
  • APPRISE_URLS Comma-separated [Apprise URLs](https://github.com/caronc/apprise#supported-notifications) OR `tag:<value>` / `tag:<value>@<configId>` for stateful routing. required
  • APPRISE_TITLE_PREFIX Prepended to the message title. Default `peepshow`.

Use with an LLM agent

Every peepshow sink reads its config from env vars and receives a single JSON payload on stdin. An LLM agent (Claude Code, Cursor, Windsurf, Gemini, Codex) can drive the Apprise sink automatically when three things are true:

  • the env vars below are exported in the agent's shell (or a project .env it can load),
  • the peepshow CLI is on PATH — install with npm i -g peepshow,
  • a peepshow auto-sink is registered for the run (optional but recommended — makes invocation zero-argument).

1. Set the environment

# Add to ~/.zshrc, ~/.bashrc, or a project .env the agent can load
export APPRISE_BASE_URL="..."
export APPRISE_URLS="..."

2. Register as an auto-sink

peepshow sinks add apprise
peepshow sinks add apprise --when extension=mp4,mov

3. Example LLM session

You → drop a .mov into Claude Code.

Claude → auto-invokes /peepshow:slides ./clip.mov. peepshow extracts frames + audio, the Apprise sink forwards the run to the configured channel. Claude replies with a summary and a link to the created record.

The transcript snippet is posted alongside the frames as a secondary message.

Write your own

A sink is any executable that reads the --emit json payload on stdin. Shell, Node, Python, Go — the spec's in docs/PLUGINS.md. Register persistent ones with peepshow sinks add-cmd 'your-command'.