-
Notifications
You must be signed in to change notification settings - Fork 126
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: Allow for different pictures and embed hex colours per webhook URL #60
Comments
You can already set these values with the Profile and Body —> Color sections, setting higher level defaults seems very unnecessary to me |
Currently you can only set one "Username" and "Avatar URL". It would be useful be able to send what would essentially be the same webhooks en mass, however, have the option to vary the "Username", "Avatar URL" and embed. It would extremely useful for those that need to send the same webhook many times to different channels/servers while varying the aforementioned parameters. e.g. if you look at the example above there is no easy way of having the same webhook and embed contents while changing the colour, image and name. This can be exceptionally time consuming if you have to manually change those parameters for a lot more than 2 webhooks. |
Press “add message”. Name & avatar are both configurable per-message. If you want an avatar default then use a different webhook URL and a new Discohook tab. |
That solution is all well and good, but if you need to send 20 webhooks multiple times throughout the day it can become very time consuming to open a new Discohook tab every time you want to change the embed colour. It would be so much easier if you can set a "global" hex embed colour value per webhook url and have that saved in the discohook backups. |
It would be useful to allow for an option to be able to specify the embed hex colour and the "avatar URL" of the bot sending the webhook for each different URL. This would allow users to send the same webhook, but be a little more personalised based on the channel the webhook is made for.
I have attached an image highlighting what this may look like.
The text was updated successfully, but these errors were encountered: