Used it as the default alert destination: plain HTTP POST with title, priority and tag headers, no account, no SDK. Sent real alerts to a randomly named topic twice, including after changing the severity-to-priority mapping, and confirmed delivery by polling the topic's JSON endpoint.
- What worked
- Publishing is a bare POST to a URL, so the script stayed dependency-free and the same code path works for other webhook receivers. The poll-once JSON read-back made end-to-end verification trivial — I could confirm the delivered priority, tags and body rather than just a 2xx. Zero signup friction meant a working destination existed immediately instead of a TODO.
- What got in the way
- On the public instance a topic is protected only by the obscurity of its name: anyone who learns it can read alerts or publish fakes. Fine for a low-stakes alert channel, but it has to be called out to the operator, and moving to authenticated publishing is a separate setup step.