Webhook to XML Payload with WhatsApp Notification
Turns incoming webhook JSON into a formatted XML document and pushes the result straight to a WhatsApp number so nobody has to watch the endpoint.
Use this templateWhy use it
A partner system, an order platform or an internal script keeps firing JSON at an endpoint you set up, but the system on the receiving end of your process only reads XML. So somebody exports the payload, reshapes it by hand or runs a one-off script, and then pings a colleague to say it arrived. Half the time nobody checks the endpoint for hours, a batch sits unnoticed until a customer complains, and when something does break there is no record of what actually came in. It is a small task that keeps interrupting the day and still manages to go wrong.
How it works
- 1An endpoint sits waiting for incoming data. Whenever the other system posts its JSON payload, the flow picks it up immediately — no polling, no scheduled check, no one refreshing a dashboard.
- 2The raw JSON is restructured into a properly formatted XML document, with the keys and nested values mapped across into tags, so the result is ready for a system that only accepts XML.
- 3The finished XML is sent as a WhatsApp text message through WhatsScale to the number you choose, so the person who needs it sees the payload on their phone the moment it lands.
What it connects
- Webhook
- Xml
- WhatsScale
Questions
What kind of JSON can the endpoint accept?
Any standard JSON body posted to the webhook URL will do. Nested objects and arrays are converted into nested XML elements, so you do not have to flatten the payload before sending it.
Can I send the XML to a group or several people?
The step as built sends to one WhatsApp destination that you set manually. If more people need it, you can duplicate the sending step and point each copy at a different number.
What happens if the incoming payload is very large?
WhatsApp text messages have a length limit, so a very large XML document may be truncated or rejected. For big payloads it is better to send only the fields that matter, or trim the JSON before it reaches the endpoint.
Does the XML get saved anywhere?
Not by this flow. It converts and forwards in one pass, so the WhatsApp message is the record. If you need an archive, add a storage or file step after the conversion.
Will the XML be readable in a WhatsApp message?
It arrives as plain text with the tags intact, which is fine for short structured payloads and for copying into another system. It is not pretty-printed the way a code editor would show it.
Do I need to expose anything from my own servers?
No. The webhook URL is generated for you, and the sending system just posts to it. Nothing needs to be opened up on your side beyond letting that system make outbound requests.