> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-nodes/map-node.md). # Map node ## Overview When syncing data between different systems, you define the relationship between source fields (i.e. the data fields a pipeline receives) and the corresponding fields in the target system.

Sometimes, source and target fields will be a like-for-like match (for example, `first_name` maps to `first_name`) but often, source values must be manipulated (transformed) before being sent to the target system. The *Map* node is used to define what data values to send from the source system into the target system, and any required transformations to achieve this: Using [data schemas](/documentation/brigge-for-transformers/schemas.md) to describe the structure of data in source and target systems, you can [generate mappings manually](#working-with-mapping-rows) or with [AI assistance](#creating-mappings). {% hint style="info" %} Mapped data fields are output in mapping row creation sequence. {% endhint %} ## Creating mappings {% stepper %} {% step %} **Access the mapping editor** Click the *Map* node to access settings, then click `open editor`:

{% endstep %} {% step %} **Choose source and target schemas** Select `source` and `target` schemas. For example:

Choose a schema that reflects the expected structure of incoming data. You'll notice that schemas are categorised according to where they are used:

Category	Summary
Favourites	If you have favourited schemas, a favourites category is always at the top of the schema list. You can favourite any schema from the schema selection list, for example:
Current pipeline	If the current pipeline includes nodes that are configured to use a schema (e.g a split node), those schemas are shown here.
Systems	Schemas defined for system endpoints.
Pipelines	Schemas used in other pipelines (but not this one).
Uncategorised	Schemas created from general settings and not applied to any systems or pipelines.

Data fields for the selected schemas are displayed in the left (source) and right (target) panels, ready to map. {% endstep %} {% step %} **Generate mappings with AI** Unless your mappings are particularly complex, allowing AI to take a first pass at mapping the two schemas is recommended:

Mappings are generated, with mapped fields indicated by a green marker. You can now [review the mappings and make any adjustments needed](#working-with-mapping-rows). {% endstep %} {% endstepper %} ## Working with mapping rows

Checking specific source and target mappings

To check a specific mapping, select the target field from the `outputs` panel; corresponding source field(s) are highlighted in the `inputs` panel. To continue checking another mapping, click the `clear` button to clear current selections, then choose another target field to review.

Mapping a source and target field manually

You might choose to map: * One source field to one target field (below) * [One source field to multiple target fields](#mapping-multiple-source-fields-to-a-single-target-field) * [Multiple source fields to one target field](#mapping-multiple-source-fields-to-a-single-target-field) To map single source and target fields manually, select the required fields from `input` and `output` panels, then click the `add row` button between the two panels. {% hint style="info" %} When you click a source or target field, you are selecting it to be mapped. If you make a mistake and choose the wrong field(s), use the `clear` button to clear current selections and start again. If you want to clear ALL mapped rows and start again, use the `clear mapping` button at the bottom of the map editor. {% endhint %}

Mapping one source field to multiple target fields

When one source field is mapped to multiple target fields, the same source value is output to all selected target fields. To do this, select the required fields from `input` and `output` panels, then click the `add row` button between the two panels. In this case, you will select one field on the left, and multiple fields on the right. {% hint style="info" %} When you click a source or target field, you are selecting it to be mapped. If you make a mistake and choose the wrong field(s), use the `clear` button to clear current selections and start again. If you want to clear ALL mapped rows and start again, use the `clear mapping` button at the bottom of the map editor. {% endhint %} If you then select one of the mapped target fields, all fields for the mapping row are shown.

Mapping multiple source fields to a single target field

There may be times where you need to combine multiple source fields and send the combined value into the target field. A common example is where one system outputs `first name` and `last name` and another expects a `full name`. To map multiple source fields to a single target, select the required fields from `input` and `output` panels, then click the `add row` button between the two panels. In this case, you will select multiple fields on the left, and one on the right. {% hint style="info" %} When you click a source or target field, you are selecting it to be mapped. If you make a mistake and choose the wrong field(s), use the `clear` button to clear current selections and start again. If you want to clear ALL mapped rows and start again, use the `clear mapping` button at the bottom of the map editor. {% endhint %} If you then select one of the mapped target fields, all fields for the mapping row are shown. Next, you must add [transformations](#adding-transformations) to manipulate source fields into one value, before being sent to the target. {% hint style="warning" %} You must apply [transformations](#adding-transformations) to combine multiple source fields into one. Without this step, the mapping won't work as expected. {% endhint %}

Updating an existing mapping

To add or remove a field for an existing mapping, select the row to display mapped source and target fields. To remove a mapped field, click it once (so it becomes unselected), then click the `update row` button between the two panels. {% hint style="info" %} The `update row` button becomes active as soon as you select an existing mapped row. {% endhint %}

Deleting a mapping row

To delete an existing mapping, select the row to display mapped fields and then click any mapped `source` fields (so they become unselected). As soon as a mapping row has no defined source fields, a `delete row` button becomes available between the two panels. Click this to remove this mapping row.

## Adding transformations Transforms are used to change the value, format, and/or shape of data for onward processing. They are used in different places throughout Brigge. In the *Map* node, you can define transformations to manipulate source values before they are output for the target. For example, you might need to convert a text field to numeric, lowercase to uppercase, join two separate fields, etc. A mapping row can have as many transforms as needed. When multiple transforms are applied, they are processed in sequence (so one can build on the output from its predecessor). To add a transform for an existing mapping row, follow the steps below. {% hint style="info" %} For a summary of available transformations, see [Data transformations](/documentation/brigge-for-transformers/pipelines/data-transformations.md). {% endhint %} {% stepper %} {% step %} **Select the mapping row(s) to be transformed** In the example below, the selected rows map `first` and `last` source fields to a single target `name` field:

{% hint style="info" %} Typically, transformations are used to manipulate incoming data - i.e. transforming incoming source data for onward processing. However, you can also use transformations to inject data into target fields when no source value is received. For example, a target system might require values for a `currency` field, which is not part of incoming source data. In this scenario, you might apply a [custom value](/documentation/brigge-for-transformers/pipelines/data-transformations.md#custom-value) transformation to the target field, with the required currency value. {% endhint %} For this example, we will use a transform to join `first` and `last` source field values and send the transformed value to the target `name` field. {% endstep %} {% step %} **Add a new transform** Click the 'plus' icon in the transforms section. For example:

{% endstep %} {% step %} **Choose a transform type** Use the `transform type` dropdown list to select the transformation function needed. For our example, we select the concat transform, to concatenate selected input fields:

{% endstep %} {% step %} **Configure the transformation** Required configuration varies according to the the selected transform type. For our `concat` example, the settings are:

Different transformations require different settings however, general field behaviour is common:

Field	Summary
Value to transform	Provided you selected the full mapping row before choosing to add the transformation, the default value will be the last input field in the mapping. You can choose an alternative input from this dropdown list.
Inputs	Select any inputs to be processed by the transformation. The dropdown list will include all input fields for the selected mapping, outputs for previous transformations processed for this mapping, and system variables.

In our example: * `value to transform` defaulted to last\_name but we changed it to first\_name (the first input field required in the join). * `delimiter` is entered as a space, as we need a space between first and last name values * `input field 2` is added for the second field in the join (you can add more inputs if needed). {% hint style="info" %} Remember, this is just one example of a transformation - different transform types require different settings. {% endhint %} {% endstep %} {% step %} **Confirm transform settings** Having clicked `done` to confirm transform settings, the transform is displayed in the mapping editor when this mapping row is selected. For example:

{% endstep %} {% step %} **Update the mapping row** Click `update row` to apply the transform, then save changes. {% endstep %} {% endstepper %}