Generic webhook needs to be better exposed

[talboren]

Is your feature request related to a problem? Please describe. Keep has a "generic" webhook mechanism where you can send events to Keep's API and see them in the alerts page. To see and understand the payload, we have a tab under "Settings" -> "Webhook"

Today, it's kinda "hidden" that we have this capability and we need to better expose it (either via a dedicated "provider" or via the alerts page) and add documentation about it to the docs.

Describe the solution you'd like Expose the generic webhook capability better throughout the UI (+better UX) and add documentation about this feature.

Describe alternatives you've considered

Additional context

[talboren]

@fivenp hope you can throw your 2 cents in here ❤️ 🙌🏼

[fivenp]

I think the webhook could be shown on the provider list (maybe with a special tag to it) so it becomes very obvious for people right away?

[talboren]

I think the webhook could be shown on the provider list (maybe with a special tag to it) so it becomes very obvious for people right away?

Maybe but I'm struggling with the idea on how to show it because:

1. You don't really need to "connect" this provider
2. It works kinda similar to how providers as Prometheus works:
3. We already have some kind of tag for "Webhook" supporting providers:

[fivenp]

We can easily call it "Incoming webhook" which would make a lot of questions obsolete :)

On Wed, Nov 8, 2023 at 2:35 PM talboren @.***> wrote:

I think the webhook could be shown on the provider list (maybe with a special tag to it) so it becomes very obvious for people right away?

Maybe but I'm struggling with the idea on how to show it because:

1. You don't really need to "connect" this provider
2. It works kinda similar to how providers as Prometheus works: [image: CleanShot 2023-11-08 at 15 34 39] https://user-images.githubusercontent.com/68807791/281419230-60ed5196-5739-4801-ada0-aa7497e30473.png
3. We already have some kind of tag for "Webhook" supporting providers: [image: CleanShot 2023-11-08 at 15 35 18] https://user-images.githubusercontent.com/68807791/281419350-040301e3-61a3-4f3d-82ec-5e924fc6b637.png

— Reply to this email directly, view it on GitHub https://github.com/keephq/keep/issues/466#issuecomment-1801904674, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABAJ3A4KBCHKUFY4TPP7Y3YDODC7AVCNFSM6AAAAAA7C3A4TSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBRHEYDINRXGQ . You are receiving this because you were mentioned.Message ID: @.***>

[talboren]

🤣, I guess we can do something like that and get "another provider"

[Matvey-Kuk]

/bounty 30

[algora-pbc[bot]]

💎 $30 bounty • Keep (YC W23)

Steps to solve:

1. Start working: Comment /attempt #466 with your implementation plan
2. Submit work: Create a pull request including /claim #466 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to keephq/keep!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🔴 @evonloch	Jun 8, 2024, 6:12:36 PM	WIP

[Matvey-Kuk]

This bounty is a part of our effort to welcome new contributors to the repo.

[evonloch]

/attempt #466

Algora profile	Completed bounties	Tech	Active attempts	Options
@evonloch	2 bounties from 1 project			Cancel attempt

[algora-pbc[bot]]

@evonloch: Reminder that in 4 days the bounty will become up for grabs, so please submit a pull request before then 🙏

[algora-pbc[bot]]

The bounty is up for grabs! Everyone is welcome to /attempt #466 🙌