Developer

JSON Integration

Zynk's JSON connector converts data between JSON and XML inside Zynk Workflow. Most Zynk tasks read and write XML, while modern REST APIs and many file feeds use JSON. Two conversion tasks let integration teams bring JSON into a workflow for mapping, then turn the result back into JSON for whichever API, file store or partner needs it next.

Available for

Workflow

Capabilities may differ depending on the product.

See what you can do Book a call →

Benefits

Why businesses connect JSON

Work with any REST API

Pair the JSON tasks with Zynk's HTTP task to call APIs that have no dedicated connector. Responses convert to XML for mapping, and request bodies convert back to JSON before they are sent.

Conversion in both directions

JSON To XML handles data coming into a workflow, and XML To JSON handles data going out. A single workflow can read a JSON file from one system and post a JSON payload to another.

Map with XSLT, not scripts

Once JSON has become XML, the usual Zynk tools apply: XSLT transforms and XML select, split and merge tasks. Teams reuse the mapping skills they already have instead of writing a new script for every feed.

Files as well as APIs

JSON files collected from SFTP, Amazon S3 or a local folder convert the same way, so product feeds, exports and data dumps in JSON can be loaded into accounting, ERP or database systems.

Older systems meet newer ones

Platforms that only exchange XML or CSV can feed JSON-based services, and the reverse, without either side changing. The conversion happens in the workflow that sits between them.

Capabilities

What you can do with JSON

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

Actions in JSON

Tasks Zynk can automate in JSON

2 tasks

JSON to XML → in JSON
XML to JSON → in JSON

Need something that isn't listed?

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

Talk to us

The problem

Why integrate JSON?

Integrations rarely stall on business logic. They stall on formats. One system exports XML, the next only accepts JSON, and a third sends JSON nested several levels deep. Without a standard conversion step, every new connection means custom code that someone has to maintain long after its author has moved on.

Without integration

Custom scripts written to reformat each API response
XML exports that a JSON-only service will not accept
Supplier JSON files opened and retyped into spreadsheets
Format quirks handled differently in every workflow

With Zynk

API responses convert to XML with a standard task
XML converts to JSON before it is posted
JSON files convert and map straight into your systems
One conversion approach used across all your workflows

How it works

How the JSON integration works

Step 1: Fetch or receive the JSON
Bring JSON into the workflow, either from an API call made with the HTTP task or from a file collected over SFTP, from Amazon S3 or from a local folder.
Step 2: Convert it to XML
The JSON To XML task writes the document out as XML, so its objects and arrays become elements that XSLT and the other Zynk tasks can read.
Step 3: Map and transform
Reshape the data with XSLT or the XML tasks, then pass it to the connectors that need it, such as Sage, a SQL Server database or a marketplace.
Step 4: Convert back and send
Where the destination expects JSON, the XML To JSON task builds the payload, ready for the HTTP task to post or a file task to upload.

Integrations

What can you connect to JSON?

HTTP

XML and XSLT

Remote File Transfer (FTP, SFTP)

Amazon S3

XML

CSV

File

SQL Server

Example use cases for JSON integration

JSON and HTTP

Call REST APIs with the HTTP task and convert their JSON responses into XML, or turn mapped XML into a JSON request body for the next call.

JSON payloadsAPI responses

View the HTTP integration →

JSON and XML and XSLT

Hand converted data to XSLT Transform, XML Select or XML Split for mapping, then convert the result back to JSON wherever JSON is needed.

XML documentsXML documents

View the XML and XSLT integration →

JSON and Remote File Transfer (FTP, SFTP)

Download JSON files from a supplier's SFTP server for conversion, or upload JSON files produced by a workflow for a trading partner to collect.

JSON filesJSON files

View the Remote File Transfer (FTP, SFTP) integration →

JSON and Amazon S3

Read JSON objects from an S3 bucket into a workflow and write the converted output back to S3 for other services to pick up.

JSON filesJSON files

View the Amazon S3 integration →

Find your integration →

JSON integration FAQs

How do I convert JSON to XML in Zynk?

Add the JSON To XML task to a workflow and point it at the JSON input, whether that is a file or the response from an HTTP task. It writes an XML file that the rest of the workflow, including XSLT transforms and connector tasks, can read.

Can Zynk convert XML back to JSON?

Yes. The XML To JSON task takes an XML document, often the output of an XSLT mapping, and writes it as JSON. That is usually the last step before posting data to a REST API or saving a JSON file for another system.

Why does a Zynk workflow need XML at all?

Most Zynk connector tasks read and write XML, and XSLT is a mature, well-documented way to map one structure onto another. Converting JSON to XML lets you use those tools on JSON data rather than maintaining a separate script for each format.

Can Zynk call an API that has no dedicated connector?

Often, yes. Zynk's HTTP task can call most REST APIs, and the JSON tasks handle conversion either side of the call. It takes more configuration than a dedicated connector, and our team can advise on authentication, paging and error handling.

Do I need to be a developer to use the JSON tasks?

Some technical knowledge helps. Zynk Workflow is low-code, so the conversion itself is configured rather than programmed, but mapping the converted XML usually involves XSLT. Zynk's integration team can build that part for you if you would rather not.

Can Zynk read JSON files from SFTP or Amazon S3?

Yes. Zynk's remote file transfer tasks download files from FTP and SFTP servers, and its Amazon S3 tasks read objects from a bucket. Once a JSON file is available to the workflow, JSON To XML converts it for mapping like any other input.

How do I start building JSON workflows with Zynk?

If you already use Zynk Workflow, the JSON tasks can be added to any workflow. If you are new to Zynk, book a call and describe the API or file you need to work with, and we'll show how a workflow would handle it.

See what Zynk can automate for your JSON 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 →