Q-Cloud File Parser Input Formats, Matching, and Ordering

Supported Input Formats

The parser accepts CSV and JSON files, then converts each file into the matching Q-Cloud request sequence.

With INPUT_FORMAT=auto:

  • .json files are parsed as JSON.

  • all other files are parsed as CSV.

CSV Expectations

  • 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.

Supported File Encodings

  • ASCII

  • UTF-8

  • UTF-16LE

  • UTF-16BE

  • UTF-32LE

  • UTF-32BE

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

File Matching

By default, the parser matches files using configured filename rules. Most file interfaces use a filename pattern that identifies the intended integration.

ZWZ Fileinterface is configured explicitly and does not rely on the filename alone. The parser mode determines which family of rules is active.

Processing Order

Files are processed deterministically. If a filename contains a timestamp, that timestamp is used first. Otherwise, the parser falls back to the configured file-type order and then the filename.

Example Input Directory

/tmp/qcloud/in/
  AddArticles_20260218-120001.csv
  AddItem_20260218-120002.csv
  RemoveUser_20260218-120005.csv