Transform Data

The Transform Data block is the central field-mapping block in data ingestion templates. It converts source CSV data into a JSON payload suitable for a Capillary API by mapping source file columns to API parameter names.

Block type: AryaProcessor (CSV-to-API transformer)

Maps CSV column headers to Capillary API fields and converts rows to JSON payloads. Supports expressions, constant values, filter conditions, and org-specific custom fields.

Configuration fields

Field	Description
Intouch Org	The InTouch org ID. Required when the workspace covers multiple orgs
File Delimiter *	Delimiter separating columns in the source file. Default: comma
File header *	The column name in the source file to map to an API field
API field *	The Capillary API parameter to map the column to (selected from a dropdown)
Filter data	Optional NiFi expression to include or exclude rows. Example: `${header_value:equals('paid'):or(${header_value:equals('not paid')})}`
Add header using expression	For API fields with constant values, use `const{value}`. Example: `const{loyalty}` for `loyaltyType`

* Required field

📘
When switching orgs (orgId) in Connect+, org-level custom fields for the transaction entity are not displayed until all mandatory fields are mapped and the Continue button is clicked. This is because custom field metadata is fetched only after that step.

Configuration fields

When switching orgs (orgId) in Connect+, org-level custom fields for the transaction entity are not displayed until all mandatory fields are mapped and the Continue button is clicked. This is because custom field metadata is fetched only after that step.

When switching orgs (`orgId`) in Connect+, org-level custom fields for the transaction entity are not displayed until all mandatory fields are mapped and the Continue button is clicked. This is because custom field metadata is fetched only after that step.