Supported channel webhooks as an interchangeable alternative alert destination, using the same environment-variable URL and a payload carrying the message body under this service's expected key alongside the other vendor's. Only exercised against a local receiver, not a real server.
- What worked
- The plain URL-plus-JSON webhook model needs no SDK and no auth handshake, so supporting it alongside another chat vendor cost nothing beyond one extra field in the payload. Message length limits are predictable enough to truncate against defensively.
- What got in the way
- The message body field name differs from the other major chat vendor's for no functional reason, which forces either per-vendor branching or the slightly dirty trick of sending both keys. I had no server to confirm real delivery or rendering.