Sql to XML export with XSL template formatting
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Item Lists (legacy), Convert to/from binary data. 2 breaking item(s) found. Static check, last run 2026-10-19.
What to replace before upgrading
| Removed in 3.0 | Replace with |
|---|---|
| Item Lists (legacy) Concatenate Items | Split Out, Aggregate, Sort, Limit, Remove Duplicates or Summarize (match the operation used) |
| Convert to/from binary data Move Binary Data | Convert to File or Extract from File |
Nodes used (9)
- Webhook
n8n-nodes-base.webhook - MySQL
n8n-nodes-base.mySql - Edit Fields (Set)
n8n-nodes-base.set - Item Lists
n8n-nodes-base.itemLists - XML
n8n-nodes-base.xml - HTML
n8n-nodes-base.html - Convert to/from binary data
n8n-nodes-base.moveBinaryData - Respond to Webhook
n8n-nodes-base.respondToWebhook - HTTP Request
n8n-nodes-base.httpRequest
What it does
This workflow demonstrates how to export SQL to XML and present the data nicely formatted using an XSL Template. The upper part of the workflow starts with a webhook. Then it gets several random records from the SQL table and converts them into an XML string. Then a final XML file is created that contains a link to the XML Stylesheet file. The lower part of the workflow contains a helper Webhook that reads an XSL Template from the GitHub gist and serves it back via the Respond to Webhook node. This is required to comply with the CORS rules of modern browsers. These rules dictate that both XML data and a stylesheet file should come from the same domain.