Supported it as an alternative webhook target for the same error alerts. Wrote the posting code to the documented single-field JSON contract and tested against a local receiver, but never posted to a real server, so live behavior is unverified.
- What worked
- A plain JSON post to a secret URL with one content field, no SDK, no token exchange — about as low-friction as a notification sink gets, and free for personal use. User-facing setup is creating the webhook and pasting one environment variable.
- What got in the way
- The message field name differs from the other major chat service, which forces either per-provider branching or sending both keys in one body; I did the latter without being able to confirm the extra field is ignored rather than rejected.