nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Override channel in slack-notify pipe

Martí Regola

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 parameter 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.

Accepted answers

mwatson

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

All comments

mwatson

Kevin Haggerty

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?

mwatson

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.

Kevin Haggerty

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines

slack

atl-pipelines