-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Discord compatibility with Slack webhook or new Discord integration in Ghost #9246
Comments
Hey @ScarletWolf275 👋 Thanks for your interest and suggestion. In general feature requests should be suggested and discussed in slack, however in this case your suggestion sounds like a simple enhancement of the existing slack url validation. cc @kevinansfield Is that something we could label as community enhancement? |
This has been raised previously, see #7856 |
@ScarletWolf275 there's a few missing pieces of information here.
|
Discord requires a postfix for every service. It can receive messages from slack. But that can be manipulated. For example I have |
@ScarletWolf275 in case you didn't see the 1.17.3 release has a fix for this, you are able to put any valid URL into the Slack app webhook field so it will work for Discord, Mattermost, and any others 👍 |
Alright. Thanks! |
Issue Summary
This is a feature suggestion, and an issue. Right now, I don't use Slack, I use Discord. Discord's webhook implementation is the same as slack. For Gitlab, they don't have Discord but I can put my discord webhook followed by a /slack and it will work normally in Gitlab's slack service. I wish the same could happen here, I try to paste my discord web hook followed by /slack in Ghost and it is limiting how the URL is. It is restricting it to be https://hooks.slack.com. I need an easy way of using that option with Discord to notify my community about the new blog posts.
Steps to Reproduce
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:
The text was updated successfully, but these errors were encountered: