Convert
The Convert step transforms data from one shape into another using a pre-configured
mapping. It is the workhorse of most integrations: take what arrived, produce
what the destination expects.
Configuration
| Field | Notes |
|---|---|
| Mapping | The mapping to apply. Its input and output data types determine what this step accepts and produces |
| Value / Value Type | The data to convert — a literal, a variable, or an earlier step's output |
| Input Delimiter | The field delimiter of the incoming data, for delimited input |
| Output Delimiter | The delimiter to write, for delimited output |
| Entry Offset | How many rows to skip before reading — used to step past a header or preamble |
| Condition to Apply | Restrict the conversion to records meeting a condition defined on the mapping |
| Include headers | Write a header row in delimited output |
| Include empty columns in output | Keep columns that produced no value, rather than dropping them |
| Write to file | Send the result to the Intely File System instead of carrying it in the run |
Output
The converted data, ready for the next step. Mapping inputs appear as their own fields on this
step, so a mapping expecting several inputs is filled in here rather than assembled beforehand.
Notes
- Crosswalks, filters and conditions are configured on the mapping, not on this step — see
Mappings and Crosswalks. - Include empty columns matters for fixed-shape deliveries: a partner expecting a stable
column count will reject a file whose columns shift when a value is absent.
Updated 10 days ago
Did this page help you?
