[🐛 Bug]: PostgreSQL provider documentation link leads to wrong or missing page

[gecube]

Summary

In the list of available providers, PostgreSQL appears as a supported integration.
However, clicking the Documentation link opens an incorrect / non-existent page:

❌ Current broken link:
https://docs.keephq.dev/providers/documentation/postgres-provider

✅ Expected correct link:
https://docs.keephq.dev/providers/documentation/postgresql-provider

The current link results in an empty page or 404.

---

🧩 Steps to reproduce

1. Open KeepHQ web UI
2. Navigate to Integrations → Providers
3. Find the PostgreSQL provider
4. Click Documentation

Expected:
Documentation or setup guide for PostgreSQL provider opens correctly.

Actual:
Redirect to missing page (postgres-provider) with no content.

---

💡 Expected behavior

The documentation link for PostgreSQL provider should:

• point to the correct page
  → https://docs.keephq.dev/providers/documentation/postgresql-provider
• or be hidden if no documentation yet exists

---

✅ Proposed fix

• Update the URL in provider metadata from postgres-provider → postgresql-provider,
  or
• Provide at least minimal placeholder content at the current link to avoid confusion.

---

Labels: type:bug area:documentation priority:low

[dosubot[bot]]

The broken PostgreSQL provider documentation link is caused by how the KeepHQ UI dynamically generates the URL using the provider's type (postgres), resulting in /providers/documentation/postgres-provider, which does not exist. The actual documentation is at /providers/documentation/postgresql-provider and contains all the expected setup and usage details citation.

The link is constructed in the frontend code (ProviderForm component) like this:

href={`${
  config?.KEEP_DOCS_URL || "http://docs.keephq.dev"
}/providers/documentation/${provider.type}-provider`}

To fix this, update the link logic to use the correct slug (postgresql-provider) for the PostgreSQL provider, either by adding a mapping or adjusting the provider type. There is no existing override or mapping for documentation links in provider metadata citation.

If you want to avoid confusion until this is fixed, you could add placeholder content at the broken link, but the best solution is to update the link logic to point to the correct documentation page.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}