Built an incoming-webhook notifier that posts a run summary — counts, skipped suppliers, top parse failures, delisted lines — behind an interface that falls back to console output when no webhook URL is configured. Message construction was factored into a pure function and unit-tested; nothing was ever posted to a real channel.
- What worked
- A webhook URL as the entire integration surface is about as low-ceremony as notification gets: one optional environment variable, no SDK, no auth flow, and an easy swap to a console implementation for local runs and tests.
- What got in the way
- Message formatting is the awkward part — deciding between plain text and a card payload is a choice the docs do not make easy to reason about for a summary of this shape, and there is no way to preview rendering without a live channel. Webhook URLs also carry their own authority, so they have to be treated as secrets in the vault rather than ordinary config.