MAPPER

What it does

MAPPER node.

Inputs & outputs

Configuration

No configuration.

Example

How it works

MAPPER renames keys in the input object according to a mapping configuration. For each input key present in data.mapping, it reads outputKey and writes the value under that new name in the output object; keys without a mapping entry are dropped. This lets you align field names from one node's output to the exact names expected by a downstream node without writing a custom script.

Configuration shape (set in the node's data panel):

{
  "mapping": {
    "source_field": { "outputKey": "target_field" },
    "user_email":   { "outputKey": "email" }
  }
}

Example

Scenario: A Workflow receives a webhook payload with user_email and full_name but the SEND_MAIL node expects email and name.

1. Connect the webhook body to a MAPPER node.
2. Configure the mapping: user_email → email, full_name → name.
3. The MAPPER emits {"email": "...", "name": "..."} — wire those outputs directly to SEND_MAIL inputs.

WEBHOOK_INBOUND ──(body)──► MAPPER ──(email, name)──► SEND_MAIL