I was wondering if there is an option to override the channel on the slack-notify Pipe. Now the pipe only sends notifications to the default channel.
It is possible on the manual messages passing "channel": "#other-channel" in the payload.
If there is nothing configured it would be a nice feature to add as an optional para
meter in the pipe configuration.
That would solve the need of creating more and more Webhooks to send messages in different channels with the same topic.
The way to do this is to register a different incoming webhook that maps to the channel you want to notify - essentially the target channel in encoded in the WEBHOOK_URL itself - see step 3 of the slack docs here: https://api.slack.com/incoming-webhooks
But why not support an optional channel parameter for cases where you don't want to have a million webhooks defined (one for each channel) and instead just have one where you override the channel when you send the message?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good idea, but unfortunately, this is just how it works in Slack - they use the webhook url to define which channel the message is for. Nothing we can do on our end.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, we've got lots of webhooks that explicitly specify a channel (as you noted), but you can easily override the channel as noted above in the original report.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.