WhatsApp Flows to be Added for WhatsApp Nodes

Feature Requests
,
1

The idea is:

Send WhatsApp Flows in addition to Template and Other Messages
Process completion responses and post data to any other node

Send Flows:

I think it would be beneficial to add this because:

Any resources to support this?

Are you willing to work on this?

We are willing to work but we do not have prior experience handling with node building

2

Subject: Suggestion to Add flow Subtype in WhatsApp Node + Temporary Solution via HTTP Request

Hi n8n community,

I’ve been working with WhatsApp templates that use the flow subtype for buttons, especially for feedback and catalog functionalities. Currently, the flow subtype is not available in the n8n WhatsApp node, which limits the ability to trigger automated flows directly from buttons in templates.
Or at least I haven’t been able to do it.

Suggestion:

It would be highly beneficial if the n8n team could add support for the flow subtype in the WhatsApp node. This feature is essential for triggering automated workflows directly from WhatsApp, enhancing user interaction and engagement.

Temporary Workaround:

In the meantime, I’ve found a workaround by using the HTTP Request node to send these templates. Below are two examples of JSON payloads you can use to send WhatsApp messages with flow and catalog buttons.

1. For Feedback Templates:

Endpoint: https://graph.facebook.com/v14.0/{phone-number-id}/messages

JSON Payload:

  "messaging_product": "whatsapp",
  "to": "recipient-phone-number",
  "type": "template",
  "template": {
    "name": "name_template",
    "language": {
      "code": "en"
    },
    "components": [
      {
        "type": "button",
        "sub_type": "flow",
        "index": "0",
        "parameters": [
          {
            "type": "payload",
            "payload": "FLOW_START"
          }
        ]
      }
    ]
  }
}

2. For Catalog Templates:

JSON Payload:

  "messaging_product": "whatsapp",
  "to": "recipient-phone-number",
  "type": "template",
  "template": {
    "name": "name_template",
    "language": {
      "code": "en"
    },
    "components": [
      {
        "type": "button",
        "sub_type": "catalog",
        "index": "0"
      }
    ]
  }
}

This method has been working well for me as a temporary solution. I hope this helps others facing the same issue. Looking forward to seeing this feature added to the WhatsApp node in the future!

Best regards :wink:

2 Likes
3

would really appreciate if you could share ur workflow code to see how you get it to have a whatsapp chat flow chain?

4
1 Like
5

so this basically allows you to have a flow interactive chat with WhatsApp bot without making the workflow start from the beginning but how does it know that the current session is still in play?