The WhatsApp integration doesn’t seem to handle messages of type order. The original payload is lost, so it’s not possible to trigger custom logic based on it. Is there any plan to support this or a way to access the raw message type/payload? https://cdn.discordapp.com/attachments/1484342435059597472/1484345175806316829/Screenshot_2026-03-20_001457.png?ex=69bde3ab&is=69bc922b&hm=e356707a257cd5447afada34d6d12f02b34c9d70937d07affcc9de572746b537&

Taking a look @many-addition-67187

Hello

When a user sends an order‑related interactive message, the integration maps it to a generic button payload and you can only read the raw data through event.payload You can: Read the raw payload: > In any node after a user message, inspect event.payload (and any tags) to get the data that was sent. This works for all mapped types, including the button types listed above. Use a custom webhook: > Create a webhook that receives the raw WhatsApp webhook payload directly from Meta, then store the needed fields in a variable for later use in your workflow.

Okay, I will try the first approach Thanks @loud-crowd-60573

Thanks for the update @loud-crowd-60573 ! Looking forward to this feature being available 👊

So do I! 😄

@loud-crowd-60573 👋 If you don’t mind, I would like to know when the feature will be deployed so I can decide whether to wait for it or implement a workaround in the meantime

Sounds good, I'll keep a close eye on the ticket and let you kow when an update comes