[Suggestion] Add more options for the webhook

[Andre601]

I think this Action could benefit from more options to be available (depending on how difficult they are to implement of course.)

Author in embed

Maybe have options like author_name, author_url and author_avatar to add the author-object within the webhook itself.
author_url and author_avatar could be optional when author_name is used since they can be set to null.

Title

Similar to the Author, but with the title option instead.
Names could be title and title_url, which would be the title (text) and URL to link in the title respectively. Url would be an optional thing.

Thumbnail and Image

A thumbnail and image option would be good to add images to the embed itself.

Fields.

This would probably be the most difficult ones and I honestly can't quite see a scenario where this could be used, but I want to suggest it anyway. xD

Auto-cut text

I don't know if this action auto-cuts text if it is too long for a webhook. If it is, ignore this, if not, maybe consider adding it, to prevent errors.

[rjstone]

Ok, I'll have to look into the webhook json format more to see what can be done. Originally the idea was to try to support everything but not necessarily use everything by default.

[melyux]

Is there a way to add an image right now?

[rjstone]

I'll check on this and see if it's possible to supply an image, but it might not be an option in Discord's API. Maybe it's already possible with Markdown?

[Andre601]

Discord allows to set a webhook's name and avatar in a request.
Also thumbnails and images via urls in an embed.

[rjstone]

Ok, right now I'm thinking maybe, in addition to the "easy mode" of being able to set some individual fields, I should also just add a single input for a JSON embeds[] array. (Maybe it could be done in YAML too, or maybe I could try to parse both, but in either case it has to be passed as one big string and so YAML is more likely to run into issues due to whitespace sensitivity in this kind of odd case.)

If it exists, the resulting array of objects would just get the additional embed pushed on the top (if "severity" is not "none" and thus the embed should be created) and then have it's length truncated at 10 (discord limit). Then some individual fields would get truncated at discord's limits and the whole thing would be checked for being within the overall size limit.)

This way anything new added to the api would probably not require any code changes except maybe an upgrade of discord.js or something.