WebHook Trigger for SOAP WebServices

[PeterW]

Hello,

I wanted to use the Webhook Trigger for incoming WebService calls, which are by default in XML (SOAP) as POST Request. They are defined by WSDL,
How do I need to tune the Webhook parameters to have the body as XML for the next node in the flow. Because when I use {{$json.body}} expression it gives me:
[Object: {“soap:envelope”: {“$”: {“xmlns:xsi”: “http://www.w3.org/2001/XMLSchema-instance”, “xmlns:xsd”: …

but I need

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope
xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”
xmlns:xsd=“http://www.w3.org/2001/XMLSchema”
xmlns:soap=“http://schemas.xmlsoap.org/soap/envelope/”>
soap:Body …

Or is there another type of Trigger, which accepts this.

This is on the n8n.cloud (Evaluation) environment.

Regards
Peter

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[BramKn]

Welcome to the community!

Maybe this option:

[PeterW]

How then to drag drop the raw data from webhook to use in the next http request as raw body?

[PeterW]

In comparison to an “AMQP Trigger” instead of a Webhook, the raw XML message can be accessed as {{$json.body}} in the next HTTP request.

[BramKn]

The incomming data seems to be a bit weirder than normal.
You can read the binary data with an n8n node, it will convert it so you can use the data easily.
Depends on the version you have, if you search for Binary in the nodes you will find it. Probably is going to be “extract from file”

[PeterW]

Incoming XML is not weird, It is the common way of integration. And WebServices (as XML) was long time available before JSON.
But also this approach with raw Body is not working:

Receive XML from webhook (without converting to JSON with normalized tags)

Got added. Once is merged, you should be able to use the function node as in the example above.

All TAGS even with a following node TransformJSON2XML are lowercase.

[BramKn]

Was not talking about the xml. Just that it is given as binary instead of in a body.

[barn4k]

In the HTTP node instead of raw content type, use binary

[PeterW]

Thank you all, that’s working: