Request Support
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Home
/
Send Module Guides
CORE MODULE

Supported Data Formats

What you'll learn in this guide

Get a quick rundown of the three data formats you can use for batch uploads in CX Platform — XLSX, CSV, and XML — plus how to download the XML structure when you need it for your own integration.

Overview

When you're sending communications in bulk, your recipient data needs to land in CX Platform in a format it can read. The good news is you've got three flexible options to choose from, so you can work with whatever your source system spits out — no need to wrangle it into something exotic first.

Each format has its own strengths. Some are quicker for one-off sends from a spreadsheet, others are better suited to system-to-system integrations where the data needs to be structured and predictable. The right choice usually comes down to where your data is coming from and who's preparing it.

A look at each format

Here's a quick comparison of the three supported formats and when each one tends to be the best fit.

Format What it is When to use it
XLSX A standard Excel spreadsheet, with your data laid out in columns and rows. Field names sit in the header row, and each recipient gets their own row underneath. Handy when your data already lives in Excel, or when someone non-technical is preparing the file. It's the most user-friendly option if you're just opening, editing, and saving.
CSV A plain-text file where each value is separated by a comma. Same idea as XLSX — headers on top, data underneath — just stripped back to the basics. A solid choice when you're exporting from another system, working with very large files, or want something universal that any tool can read and write.
XML A structured, tag-based format that mirrors the fields you've defined in your Application. Each recipient's data is wrapped in tags that tell the platform exactly what each value is. Best for system integrations where another platform is generating the file automatically. The structure is strict, which means fewer surprises when the data lands.
JSON A lightweight, structured format that uses key-value pairs to organise your data. Like XML, it's built for machines to read, but it's quicker to write and a bit easier on the eye. A great fit for modern API-driven integrations, especially when your source system is already speaking JSON. Less verbose than XML, so files stay smaller and faster to process.

‍

Not sure which to pick?
‍If a person is preparing the file, go with XLSX or CSV. If a system is preparing it, XML is usually the safer bet because the structure is locked in.

‍

Working with a different format?
‍If your data comes out of your source system in a format that isn't on this list, we can build a custom Extract, Transform, Load (ETL) layer to handle it. Think of it as a translation step that converts your file into something CX Platform can read, so you don't have to do the heavy lifting yourself. Reach out to your CX Platform contact to talk through what's possible.

‍

Download the XML structure

If you're going down the XML route, you'll want a copy of the structure CX Platform expects. This is essentially a template that maps to the fields you've set up in your Application, so the team building your integration knows exactly what to send and what to call it.

You can download it straight from the Application:

  1. In the secondary navigation menu, click Applications to view the list of available Applications.
  2. Open the Application you want the XML structure for by double clicking it, or by clicking the Settings icon on the right of the list view.
  3. Click the Fields tab to open the field configuration for this Application.
  4. Click Download XML to save the structure file to your machine.

That's it — you've now got the XML structure ready to share with your developer or integration team. Because it's generated from the fields you've configured, it stays in sync with your Application. If you ever add, rename, or remove a field, just download a fresh copy so your integration stays accurate.

‍

In this GUIDE
Article link for H2 class