File Interfaces Overview

This section covers the file-driven integrations that can be run through the Q-Cloud File Parser. Each integration has its own file format and its own operational rules.

The file parser accepts structured files from an external system and translates them into Q-Cloud actions.

Common file rules:

  • include a header row

  • keep the column count consistent on every row

  • use the column names documented for the integration you are running

  • use the supported encoding for your file source

  • use ; for multi-value fields when the integration expects it

Compatibility notes:

  • Interface pages show both the accepted header name and the accepted alternative header name.

  • The file parser accepts either header name and maps both to the same parsed field.

  • New files may use either header name shown on the interface pages.

Available File Interfaces

File Format Rules

The parser supports the following encodings:

  • ASCII

  • UTF-8

  • UTF-16LE

  • UTF-16BE

  • UTF-32LE

  • UTF-32BE

For UTF-16 and UTF-32, include a BOM whenever possible.

Most file interfaces use CSV input. The delimiter and quoting rules are described on each interface page.

How To Use These Pages

Start from the interface page that matches your file type. That page tells you:

  • the filename pattern to use

  • which columns are required

  • which columns are optional

  • how the integration treats missing or duplicate data

  • examples you can copy into your own files