Mapper

Mapper – Create Simple Mapper

Summary (SEO Meta Description):
The Mapper processor in WeHub transfers and transforms values from inputs to outputs.
Configure input/output types, names, and mappings to normalize or restructure data.

---

Overview

The Create Simple Mapper action allows you to map fields between different inputs and outputs.
It supports simple data types (String, Number, Boolean) and lets you define direct mappings or static input/output values.

This is useful for reshaping data into a standard schema, preparing payloads for APIs, or normalizing fields across different systems.

---

⚙️ Configuration Options

Field	Type	Description
Label	String	Custom name for the node (e.g., "Map Patient ID").
Input Type	Enum	Type of the input value: String, Number, Boolean.
Input Name	String	Name of the input field.
Output Type	Enum	Type of the output value: String, Number, Boolean.
Output Name	String	Name of the output field.
Input Value	Any	Static value to use as input (optional).
Output Value	Any	Static value to use as output (optional).

---

💡 Example Use Cases

• Healthcare → Map HL7 field values into FHIR resource properties.
• Finance → Convert a transactionCode input into a normalized transactionType output.
• Ops → Standardize field naming between systems (e.g., userId → id).

---

FAQ

Q: Can I define multiple mappings in one mapper?
A: Yes, add multiple mapping rows for different fields.

Q: What if the input type doesn’t match the actual data?
A: The node fails unless corrected with a Type Converter.

Q: Can I mix static and dynamic values?
A: Yes, you can provide both context-based mappings and fixed input/output values.

---

Keywords: WeHub Mapper, Create Mapper, field mapping, data transformation, schema alignment