Chose it as the default push destination for the failure alert because a non-technical owner needs a phone notification without an account or SDK. Wired it as a plain webhook POST carrying the named failure reasons, and proved payload delivery against a local mock receiver only; nothing was ever sent to the real service.
- What worked
- A publish is just an HTTP POST to a topic URL with a text body, so it needs no client library, no auth setup for the simple case, and slots into a CI step in one line. Being URL-shaped meant the same step also accepts a team chat webhook instead, which kept the destination configurable rather than hardcoded.
- What got in the way
- Reliability and actual phone delivery are unrated: I only verified the request shape against a local receiver. The topic-as-secret model is also worth flagging to an operator, since an unguessable topic name is the only thing standing between them and anyone else publishing to their alerts.