Mapping

Turn data in one system's format into the format another system expects.

Different platforms describe the same thing differently — a WooCommerce order and a NetSuite sales order hold the same information under different field names and structures. The Mapping node applies a saved Mapping Rule to convert the incoming data into the shape the next system needs.

When to use it

• Convert a payload from a source system into a target system's format (e.g. WooCommerce order → NetSuite sales order).
• Rename fields, set constant values, combine fields, convert types, and map lists of line items.

Inputs & outputs

Input handle	One — the source data to transform.
Output handle	One — the transformed data, in the target shape.

Parameters

Parameter	Type	Required	Description
Mapping Rule	Saved rule	Yes	Which Mapping Rule this node applies. You build and save Mapping Rules in the mapping builder, then select one here.

info

A Mapping Rule is built visually in OrchaSync's mapping builder, not inside this node. The node simply points at a saved rule. The rest of this page explains what a rule is made of.

What's inside a Mapping Rule

A rule is a set of field mappings plus optional loops.

Field mappings

Each target field is filled using one of three modes:

Mode	What it does
Dynamic	Copy a value from the source data, by path (e.g. billing.email).
Static	Use a fixed value you type (e.g. "web").
Compute	Build a value by combining fields (e.g. join first and last name).

Each field can also apply:

• Type — cast the value to string, number, or boolean.
• Transform — clean the value with trim, upper, lower, or number.
• Required — flag the field as mandatory.

Loops

When the source has a list that must become a list in the target (like order line items), you define a loop:

Setting	What it does
From	The source list to iterate (e.g. line_items).
Target	The target list to produce (e.g. items[]).
Filter	Optional conditions to include/exclude items, joined with AND or OR.
Fields	The field mappings applied to each item in the list.

Example — WooCommerce order → NetSuite

Source (WooCommerce order, trimmed):

{
  "billing": { "email": "sam@example.com", "first_name": "Sam" },
  "line_items": [
    { "sku": "ABC-1", "quantity": 2, "price": "19.99" },
    { "sku": "XYZ-9", "quantity": 1, "price": "5.00" }
  ]
}

A Mapping Rule that:

• maps billing.email → customerEmail (dynamic)
• sets channel → "web" (static)
• loops line_items → items[], mapping sku → itemId and casting price to a number

Output (ready for NetSuite):

{
  "customerEmail": "sam@example.com",
  "channel": "web",
  "items": [
    { "itemId": "ABC-1", "quantity": 2, "price": 19.99 },
    { "itemId": "XYZ-9", "quantity": 1, "price": 5.00 }
  ]
}

tip

Use the mapping builder's Sample Input and Output Preview panels to test a rule against real data before you attach it to a node.