Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
Merge remote-tracking branch 'upstream/main' into add-support-buttons
Gabriel Moraes89bda239b217
diff --cc CHANGELOG.mdindex 7f26512ef,889862535..f3326ae59--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -9,10 -9,7 +9,11 @@@ and this project adheres to [Semantic V### Added+- Baileys inbound button, template quick-reply, list-row and native-flow replies arrive as `type: "text"` with a structured `button { id, text? }` on `message.received` (whatsapp-web.js still has no interactive reply fields). The REST chat-history route is whatsapp-web.js only and does not carry these fields.+- Baileys inbound business prompts that offer clickable buttons (or list rows) also carry `buttons: [{ id, text }, …]` on `message.received` (URL/call CTAs are omitted — they cannot be clicked), so choices like Sim/Não are no longer flattened away into `body` only.+- `POST /api/sessions/:sessionId/messages/click-button` sends a structured button/list reply against a stored WhatsApp Business prompt on Baileys (whatsapp-web.js returns `501`). Classic `buttonsMessage` / `templateMessage` / `listMessage` prompts are supported; native-flow `interactiveMessage` replies are unverified.+- The dashboard Chats thread renders inbound Baileys prompt `buttons` and taps them through `POST .../messages/click-button`; prompt choices are also kept in persisted message `metadata` so they survive reload for rendering. Clicking still requires the prompt to be in the engine store — an evicted prompt 404s.+ - Webhook and automation filters accept a `chatId` condition, so a webhook can be scoped to specific groups or chats instead of only to a sender ([#1634](https://github.com/rmyndharis/OpenWA/issues/1634)). Thanks @krishshah9944.### Changeddiff --cc docs/29-engine-capability-matrix.mdindex b2327dcf8,694d84841..c8ec10e0d--- a/docs/29-engine-capability-matrix.md+++ b/docs/29-engine-capability-matrix.md@@@ -393,12 -392,12 +393,12 @@@ answers 501| Method | Baileys adapter 🔧⁵ | wwjs adapter 🔧¹ | OpenWA REST || --------------------- | ------------------- | ---------------- | --------------- || `subscribeToPresence` | ✅ | ❌ lib | ⚠️ baileys only |- | `rejectCall` | ✅ | ✅ | ✅ |+ | `rejectCall` | ✅ | ❌ lib | ⚠️ baileys only || `createCallLink` | ✅ | ✅ | ✅ |- **Totals:** 113 methods → 226 adapter cells: **200 ✅, 26 ❌** (2 adapter-gaps, 24- library-limitations, 0 uncertain) across 25 methods. From the REST caller's side: **90** methods- work on any engine (89 fully supported + 2 store-backed status reads), **12** are Baileys-only,-**Totals:** 112 methods → 224 adapter cells: **198 ✅, 26 ❌** (2 adapter-gaps, 24-library-limitations, 0 uncertain) across 25 methods. From the REST caller's side: **89** methods-work on any engine (87 fully supported + 2 store-backed status reads), **13** are Baileys-only,++**Totals:** 113 methods → 226 adapter cells: **199 ✅, 27 ❌** (2 adapter-gaps, 25++library-limitations, 0 uncertain) across 26 methods. From the REST caller's side: **89** methods++work on any engine (87 fully supported + 2 store-backed status reads), **14** are Baileys-only,**9** are wwjs-only (the 2 store-backed rows excluded); `sendCatalog`, unavailable on both engines,is not exposed.@@@ -965,15 -957,15 +966,15 @@@ adapter boundary — none silently stubRecomputed from `engine-capability-matrix.ts`, `upstream-surface.snapshot.json`, and a scan of theadapter sources — re-derive the same way when anything changes:- - **113** interface methods → **226** adapter cells: **200 ✅** / **26 ❌** (2 adapter-gaps, 24-- **112** interface methods → **224** adapter cells: **198 ✅** / **26 ❌** (2 adapter-gaps, 24-- library-limitations, 0 uncertain), spanning **25** methods.- - Of the 200 ✅ cells, **10 wwjs cells carry an explicit patch dependency** (4 × 🔧² status send,-- Of the 198 ✅ cells, **10 wwjs cells carry an explicit patch dependency** (4 × 🔧² status send,++- **113** interface methods → **226** adapter cells: **199 ✅** / **27 ❌** (2 adapter-gaps, 25++ library-limitations, 0 uncertain), spanning **26** methods.++- Of the 199 ✅ cells, **10 wwjs cells carry an explicit patch dependency** (4 × 🔧² status send,1 × 🔧³ channel link preview, 1 × 🔧⁴ ready-sync, 3 × 🔧⁷ participant arity, 1 × 🔧⁹ groupdescription) and one baileys celldoes (1 × 🔧⁶ newsletter-create parse); the whole wwjs column additionallydepends on 🔧¹, the whole Baileys column on 🔧⁵ — so every row rests on a patch on each side,even though no row carries a row-level mark on both.- - REST caller's view: **90** engine-neutral (88 + 2 store-backed status reads), **12** Baileys-only,-- REST caller's view: **89** engine-neutral (87 + 2 store-backed status reads), **13** Baileys-only,++- REST caller's view: **89** engine-neutral (87 + 2 store-backed status reads), **14** Baileys-only,**9** wwjs-only; `sendCatalog` (unavailable on both engines) is not exposed.- Full engine inventory (29.5), split by the exposure legend rather than lumped: Baileys **152**socket methods — 48 wired into interface methods, 5 internal wiring, 29 plumbing, **70 ❌ not