feat(messages): add carousel + fix interactive rendering on WhatsApp Web/Desktop

[pastoriniMatheus]

Summary

• Adds carousel message support (POST /message/sendCarousel/{instance})
• Fixes buttons and list rendering on WhatsApp Web/Desktop (and iOS) by injecting the required <biz> node into the relayed stanza via Baileys' official additionalNodes option
• Makes POST /instance/logout idempotent when the instance is already closed, fixing the manager UI delete flow that always shows an error toast even though the delete itself succeeds

What changes

Carousel (new)

• POST /message/sendCarousel/{instance} — accepts up to 10 cards with image/title/body/footer and 1–3 native flow buttons each (reply, url, call, copy)
• Single-card-without-image is automatically routed as nativeFlowMessage direct (iOS optimization, mirrors the upstream WhatsApp behaviour)

Buttons & Lists (rendering fix)

The previous implementation wrapped every interactive payload in a viewOnceMessage, which makes WhatsApp Web/Desktop treat it as a view-once media bubble and discard the buttons. Plus, the legacy and modern formats need different XML <biz> nodes to render across all clients.

• buttonMessage(): now sends interactiveMessage directly (no viewOnceMessage) and attaches the interactive biz node:

  <biz>
    <interactive type="native_flow" v="1">
      <native_flow v="9" name="mixed"/>
    </interactive>
  </biz>

• listMessage(): switched from the modern interactiveMessage + single_select (mobile-only) to the legacy listMessage with SINGLE_SELECT (works on Web/Desktop/iOS/Android) and attaches the list biz node:

  <biz><list type="product_list" v="2"/></biz>

• sendMessage / sendMessageWithTyping: forward an optional additionalNodes: BinaryNode[] parameter and route top-level interactiveMessage / listMessage through client.relayMessage so the biz node actually reaches the stanza

Logout idempotency

Before: DELETE /instance/logout/{instance} returned 400 Bad Request when the instance was already disconnected. The manager UI calls logout before delete, so users always saw an error toast on the delete flow.

After: returns 200 SUCCESS with "Instance was already disconnected" — the delete flow is clean.

Manager UI helper (test panel)

A small vanilla manager/dist/assets/test-interactive.js injected via index.html adds a "🧪 Test Interactive" button to each instance card. Clicking opens a modal with 5 tabs (Reply / CTA / PIX / List / Carousel) — each tab pre-fills a valid editable JSON payload and a destination number field. Useful for QA without leaving the manager.

If the script can't detect a card (the upstream React layout changes), it falls back to a floating action button with an instance picker.

Drive-by fixes

• Undefined maxRetries reference in a verbose log inside the messages.update handler
• Two pre-existing _ is-defined-but-never-used violations in chatwoot.service.ts (auto-fixed by eslint --fix)

Files

Path	Kind
src/api/integrations/channel/whatsapp/helpers/interactiveMessage.helper.ts	new
manager/dist/assets/test-interactive.js	new
manager/dist/index.html	adds <script> tag
src/api/integrations/channel/whatsapp/whatsapp.baileys.service.ts	core changes
src/api/dto/sendMessage.dto.ts	CarouselCard, SendCarouselDto
src/validate/message.schema.ts	carouselMessageSchema
src/api/controllers/sendMessage.controller.ts	sendCarousel
src/api/routes/sendMessage.router.ts	POST /sendCarousel
src/api/controllers/instance.controller.ts	logout idempotent
src/api/integrations/chatbot/chatwoot/services/chatwoot.service.ts	drive-by lint fix

Test plan

• npx tsc --noEmit clean
• npm run lint:check clean
• Manual smoke test on a real WhatsApp account, sent every kind to one mobile number:
  • Buttons: 3 reply, 2 CTA (url + copy), 1 PIX (payment_info)
  • List with multiple sections (renders on Web ✅)
  • Carousel with 3 image cards
  • Carousel with 1 card without image (rendered as buttons via the iOS optimization path)
• All five kinds render with their buttons on Web, Desktop, iOS and Android
• Manager UI delete flow: clean toast, no spurious errors when instance was already disconnected

[sourcery-ai]

Sorry @pastoriniMatheus, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery