Mapping defines how data changes as it moves between the steps of a flow or API: which source fields feed which destination fields, and how values are merged back into the record. integrator.io has five mapping types and two mappers, Mapper 1.0 and Mapper 2.0. This article helps builders choose the right mapping type for a step and the right mapper for an import.
Mapping types
Each step type has its own mapping type, and each opens from the step it applies to.
| Mapping type | Applies to | What it does | Configure it |
|---|---|---|---|
| Import mapping | Import step | Maps fields in the source record to fields in the destination application's record. | Configure import mapping in Mapper 1.0 or Map data with Mapper 2.0 |
| Results mapping | Lookup step | Merges the records a lookup returns into the source record. | Configure results mapping |
| Response mapping | Import step | Merges the import's response, such as a new record ID or an error, into the source record. | Configure response mapping |
| API response mapping | API response step in API builder | Maps source data to the fields of the API response schema. | Map an API response in API builder |
| Tool output mapping | Tool output step in a tool | Maps fields from the record to the tool's output schema. The mapper is Mapper 2.0. | Map data in a tool |
Results mapping and response mapping both add data to the source record for later steps. Use results mapping after a lookup step and response mapping after an import step.
How imports send records
An import maps one record at a time and sends one request for each record. A scheduled export sends each record it retrieves to the import separately. A real-time flow carries one record, and that record can contain many items. To map several items in one record, use an array in the record. See Iterate over an array in Mapper 2.0.
Mapper 1.0 and Mapper 2.0
Both mappers configure import mapping. Mapper 1.0 maps one source field to one destination field per row and opens a settings pane for each row. Mapper 2.0 shows the destination JSON structure you're building next to a sample of your source data, and supports nested objects and arrays.
| Mapper 1.0 | Mapper 2.0 | |
|---|---|---|
| Layout | Source record field and Destination record field columns | Destination, Type, and Source columns in a JSON structure |
| Nested objects and arrays | Not shown as a structure. A destination path such as address.city or items[*].sku builds nested output. |
Supported as a structure you build and see |
| Data type validation | Data type list per field | Data type for each source and destination field |
| Available for | Imports | HTTP and REST API-based imports, and file transfer imports such as FTP, AS2, and Google Drive |
| Field settings | Mapper 1.0 field mapping settings | Mapper 2.0 field settings |
Which mapper opens
- Mapper 2.0 opens by default for an import that has no saved mappings.
- An import with mappings only in Mapper 1.0 opens in Mapper 1.0.
- An import with any mapping in Mapper 2.0 opens in Mapper 2.0, even if Mapper 1.0 also has mapped fields.
What runs
You can enter mappings in both mappers. When you save, integrator.io saves both, but the flow runs only the Mapper 2.0 mappings. To use your Mapper 1.0 mappings, delete all mappings in Mapper 2.0, confirm that JSON structure is set to record { }, and save.
The API response mapper in API builder and the tool output mapper both use Mapper 2.0 only.
Learn more
For hands-on training, see Exploring Flow Builder.