Skip to content

feat: plugin-flow-builder return text messages instead of whatsapp me… #3091

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master-lts
Choose a base branch
from

Conversation

Iru89
Copy link
Contributor

@Iru89 Iru89 commented Aug 14, 2025

Description

I first tried to make the change in the Multichannel, but it does not work well and does not chain the changes. For example if you send a list to Webchat it works correctly and sends a text with buttons but if you send a list to Facebook it doesn't work well because the Multichannel should make two changes:

  1. change the list to a text with buttons.
  2. change the buttons for quick replies. (here fails)

Second approach make the plugin-flow-builder not to use specific WhatsApp messages when the channel is not WhatsApp. This way when the message arrives to the Multichannel it will be a normal text message and multichannel only apply change in buttons (character limits, change buttons for quick replies), markdown

To document / Usage example

Captura de pantalla 2025-08-06 a las 18 51 19 Captura de pantalla 2025-08-06 a las 18 52 10
  • With this second approach works as expected. In Facebook recibe a text message with 4 quick replies when bot send a WhastAppButtonList
Captura de pantalla 2025-08-14 a las 13 05 14

@Iru89 Iru89 self-assigned this Aug 14, 2025
@Iru89 Iru89 marked this pull request as ready for review August 14, 2025 11:05
@Iru89 Iru89 requested review from asastre and AlbertGom August 14, 2025 11:05
@Iru89 Iru89 requested a review from vanbasten17 August 14, 2025 11:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants