Skip to main content

Mapping

Two systems rarely describe the same thing the same way. A WooCommerce order and a NetSuite sales order hold the same facts under different field names and structures. Mapping is how OrchaSync converts one into the other.

Mapping Rules​

A Mapping Rule is a reusable definition of how to turn a source shape into a target shape. You build it visually in the mapping builder, test it against sample data, and then apply it inside a workflow with a Mapping node.

A rule is made of two things:

  • Field mappings — how each target field is filled (copy a value, set a constant, or compute one), plus optional type casting and transforms.
  • Loops — how to turn a list in the source (like line items) into a list in the target.

The build-test loop​

The mapping builder gives you a Sample Input panel and a live Output Preview. Paste a real source payload, watch the output update as you define fields, and adjust until the output matches what the target system expects — before you ever attach the rule to a workflow.

Using a rule in a workflow​

Once saved, a rule is applied by a Mapping node: the node takes the incoming data, runs it through the rule, and outputs the transformed result for the next node.

In this section​

  • Field mappings — dynamic / static / compute, transforms, type casting, required fields.
  • Loops — mapping lists of items with optional filters.