2

Slack notifications not usable for slack-compatible APIs

  • Live

Avatar
Yann Portier

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"'

A

Activity Newest / Oldest

Avatar

Andreas

Hi,

we use Mattermost as a self-hosted alternative which provides slack compatible webhook endpoints. An example URL looks like:

chat.mydomain.de/hooks/ocenfji73ad3adsfadsfi3dn9pxxo

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
Andreas


Y

Yann

Works well, thanks !


Avatar

Dennis

Fixed!


Avatar

Dennis

Status changed to: Live

Avatar

Dennis

Status changed to: In progress

Y

Yann

Sadly you modified the slack configuration page to allow adding a channel name, but this dumb url filter is still there anyway.


Avatar

Yann Portier

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=


Avatar

Yann Portier

Yes, it's designed to work exactly the same way so that we can benefit from all the apps that send slack notifications - zulip.com/integrations/doc/slack_incoming


Avatar

Dennis

Is this self-hosted solution, using a specific pattern/URL? Is it a own domain?


Avatar

Dennis

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?


Avatar

Dennis

Status changed to: Under review