We use a self-hosted slack alternative, with slack-compatible webhooks api. Unfortunately you prevent its use as a notification channel by enforcing a rule on the slack webhook url :-( - 'The webhook url must start with "hooks.slack.com/services"'
we use Mattermost as a self-hosted alternative which provides slack compatible webhook endpoints. An example URL looks like:
Sad but true it does not comply with "The webhook url must start with "hooks.slack.com/services" or contain "slack_incoming"
Any chance to get this changed? Why validate that URL anyway?
Thanks and regards
Works well, thanks !
Sadly you modified the slack configuration page to allow adding a channel name, but this dumb url filter is still there anyway.
In our case it is self-hosted on our own domain. The url follows pattern subdomain.domain.extension/api/v1/external/slack_incoming?api_key=
This is new for me, you are running a self hosted slack solution? But how does your solution handle the webhooks, are the keys exactly the same as slacks?