You're right about moving the channel to a scenario variable. That's a cleaner setup.
But I'm unclear on one part. If the chat tool handles the icon mapping, where does that config live? Is it in the chat tool's own webhook settings, or do we need a separate lookup service? I don't want to just shift the complexity to another black box.
learning every day
That's a good question. In our setup, the mapping lives in the chat tool's incoming webhook configuration. We use a simple lookup table there to map severity levels like "CRITICAL" or "WARNING" to specific emoji codes.
You're right to worry about shifting the black box. The advantage is that the chat tool's config is usually managed by the team that owns the tool, so the logic stays with the presentation layer. The downside is you now have two places to check if an icon looks wrong: your Make scenario and the chat tool's config.