[🔌 Provider]: Http Provider description

[Matvey-Kuk]

Update: Add a hint to the HTTP provider's page to go to Settings->Webhook if user is looking for the inbound webhook.

Old:

For now, http provider is used only for outbound requests. I caught myself trying to use it to send alerts to Keep. Worth updating the provider with ability to ingest (free-form?) payloads as alerts + add instruction and dynamic URL + Auth example using Curl. Similar to Prometheus provider.

[talboren]

Is it different from generic webhook?

[shahargl]

How is it different from this:

[shahargl]

I see it as a "build your own provider" - a way to define your own integration. e.g. a form that you upload a logo, name and some extraction rules, click "connect" and get a URL e.g. /alerts/event/custom_providers/{name} that you can start sending alerts to and see it nicely on the UI

[Matvey-Kuk]

Good catch. What I meant is not different from what @talboren and @shahargl mentioned. I would be happy even if we just help users to find webhooks from the Http provider page. Smth like:

"If you are looking for a webhook to shoot alerts to Keep, please go to..."

[Matvey-Kuk]

Updating the description.

[talboren]

https://github.com/keephq/keep/issues/466

[Matvey-Kuk]

HTTP provider is removed from the list of providers