Normalize customer records before loading

Rename inconsistent fields, stamp normalization metadata, and emit a clean record for loading.

What the workflow does

Rename inconsistent fields, stamp normalization metadata, and emit a clean record for loading.

Graph

  1. rename uses data.rename-keys.
  2. stamp uses data.set-fields.
  3. log uses console.log.

Why this boundary works

Every node has one visible job, and the edges carry only the data needed by the next step. Replace any native node after import when your production contract needs stricter validation.

Before production

Add input validation, name the retry boundary, and connect real credentials only in the destination environment.

Try it in Octonode

Use the Community catalog as a starting point, then keep the imported copy small enough to understand in one sitting.