Developer

XML Integration

Zynk's XML integration is the format converter at the edges of a workflow. It turns CSV files and JSON payloads into XML, converts XML back into JSON for web APIs, and translates EDIFACT D96A messages to and from XML for trading partners. It suits teams feeding legacy exports, web services and EDI partners into Sage, ERP and ecommerce systems.

Available for

Workflow

Capabilities may differ depending on the product.

See what you can do Book a call →

Benefits

Why businesses connect XML

CSV exports become usable data

The CSV To XML task reads a delimited file, with or without a header row, and writes structured XML. Spreadsheet exports and reports from older systems can then feed any Zynk connector instead of being retyped into another system.

JSON in and out

JSON To XML converts responses from web services into XML, adding a root element when the source has none. XML To JSON works the other way, so data prepared in a workflow can be posted to an API that only accepts JSON.

EDI without a separate translator

EDIFACT D96A messages convert to XML for processing and back again for your trading partner. The XML layout matches the one used by Zynk's Amazon Vendor Central connector, so the same downstream steps can handle both.

One structure for every later step

XML is the format Zynk works in, so most connector tasks read and write it. Converting incoming data at the start of a run means mappings, transformations and imports only ever deal with one structure, whatever format the data arrived in.

Conversion as a workflow step

Each conversion is a task in Zynk Workflow, chained with file pickup, transformation and import tasks. Input defaults to the previous task's output, so most conversions need little more than an output file name.

Capabilities

What you can do with XML

Every task the Zynk XML connector can run, grouped by the direction data moves.

Actions in XML

Tasks Zynk can automate in XML

5 tasks

CSV to XML → in XML
EDIFACT D96A to XML → in XML
JSON to XML → in XML
XML to EDIFACT D96A → in XML
XML to JSON → in XML

Need something that isn't listed?

Most XML projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate XML?

Business data rarely arrives in the shape a target system expects. A supplier sends EDIFACT, a web service answers in JSON and the old warehouse system can only export CSV. Without a common format, every pairing needs its own script, and each script becomes something only one person understands.

Without integration

CSV exports pasted into import templates by hand before every upload
Custom scripts written to read each web service's JSON
EDIFACT orders from trading partners rekeyed or sent to a paid translation service
Replies to EDI partners assembled by hand in the right segment order
A different set of rules to maintain for every file format

With Zynk

CSV files convert to XML and feed the next task automatically
JSON responses convert to XML that any connector can read
EDIFACT D96A messages convert to XML inside the workflow
XML converts back to EDIFACT D96A, with optional validation first
One XML structure for every step after conversion

How it works

How the XML integration works

Step 1: Pick up the source
The workflow collects the source data first, for example a CSV file from a network folder or SFTP site, a JSON response from an HTTP call or an EDIFACT message received from a trading partner.
Step 2: Convert to XML
The matching conversion task turns that input into XML. Settings cover details such as separators, encoding, header rows and the names of the root and row elements, so the output is predictable from run to run.
Step 3: Reshape and import
Where the layout needs changing, an XSLT stylesheet from the XML and XSLT connector reshapes the XML. The target system's connector then imports it into Sage, an ERP or an ecommerce platform.
Step 4: Convert back out
When the destination expects JSON or EDIFACT D96A, a final task converts the XML into that format, ready to post to an API or send to a trading partner, on whatever schedule the workflow runs.

Integrations

What can you connect to XML?

CSV

JSON

EDIFACT D96A

Sage 50 UK

Amazon Vendor Central

Example use cases for XML integration

XML and CSV

Convert CSV exports from spreadsheets and legacy systems into XML, choosing the column separator, quote character and whether the first row holds column names.

CSV files

View the CSV integration →

XML and JSON

Bring JSON from web services and APIs into a workflow as XML, then turn finished XML back into JSON when the destination only accepts JSON.

XML dataJSON data

View the JSON integration →

XML and EDIFACT D96A

Translate EDIFACT D96A messages from trading partners into XML for processing, and build outbound D96A messages from XML, validating the data before a file is produced.

XML documentsEDIFACT messages

View the EDIFACT D96A integration →

Find your integration →

Acorn Property Group, a Zynk XML integration customer

Customer story

Acorn Property Group automated the transfer of around 20,000 monthly invoices from iShare into Sage 50 using Zynk, freeing its accounts team from manual data entry across multiple companies.

Acorn Property Group

Read the Acorn Property Group story

Articles

Articles related to XML

Ecommerce

Your peak season preparation checklist: get your systems ready in time

Black Friday, Cyber Monday, Christmas and the post-Christmas sales are coming. Use this peak season checklist to get your integrations ready in time.

Vibe coding a Sage integration: what AI gets right and wrong

Vibe coding a Sage 50 or Sage 200 integration? Here is what AI assistants get wrong, the XML they need, and the problems to plan for.

News

Why Zynk adopted the DCMS Software Security Code of Practice

Why Zynk adopted the UK Software Security Code of Practice, and how it complements our ISO 27001 certification to protect data across every integration.

See all articles about XML →

XML integration FAQs

What is the difference between the XML and the XML and XSLT connectors?

The XML connector changes format: CSV, JSON and EDIFACT D96A into XML, and XML into JSON or EDIFACT. The XML and XSLT connector works on XML that already exists, reshaping it with stylesheets, splitting or merging files and looping through records. Most workflows use both.

Can Zynk convert CSV to XML?

Yes. The CSV To XML task converts a CSV file, or CSV text passed from a previous task, into XML. You can set the separator, the quote character, the encoding and the names of the root and row elements, and choose whether columns become elements or attributes.

How do I convert JSON to XML?

Add the JSON To XML task to a workflow and point it at the JSON file, or let it take the output of the previous task. If the JSON has no single root, give the task a root element name to use in the XML it writes.

Does Zynk support EDIFACT D96A?

Yes. Zynk converts EDIFACT D96A messages to XML and converts XML back to D96A. The outbound task can validate its input and stops without producing a file if the data fails, so malformed messages are not sent to a trading partner.

Can I convert XML to CSV with the XML connector?

XML To CSV sits in the XML and XSLT connector, next to the tasks that reshape and split XML. The XML connector covers conversion into XML from CSV, JSON and EDIFACT, and out of XML into JSON and EDIFACT D96A.

Why does Zynk use XML?

XML is Zynk's working format, so connectors read and write it and every step in a workflow can rely on the same structure. Converting incoming data early means mappings, transformations and imports are written once, however the data first arrived.

Do I need to write code to use the XML connector?

Not for the conversions themselves. Each one is a configured task in Zynk Workflow, which is low-code. Reshaping XML into a specific layout usually means an XSLT stylesheet, which our team can write and maintain for you as part of a project.

See what Zynk can automate for your XML setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a call See pricing →