Knowledge Base

Build File Transform Pipeline Workflow

Duration: ~15 min · Level: Beginner · Template: #3 File Transform Pipeline · Deployment: On-prem

Prerequisites: Local filesystem paths readable by Studio or runtime agent. See also File Drop Automation for folder-watch triggers.

Build a file processing workflow from template #3: read a JSON file, transform it, and write the result to another path.

What this template does

  1. Read Input/data/input.json.
  2. Transform — map or reshape payload.
  3. Write Output/data/output.json.

Step 1 — Load the template

  1. Studio → Templates → search File Transform Pipeline.
  2. Load template #3.

Step 2 — Paths

  1. Update input and output paths for your host (Windows or Linux).
  2. Use {{$var.dataDir}} for portable paths across environments.

Step 3 — Transform

  1. Edit the transform expression to rename fields, filter arrays, or template output.
  2. Run Dry Run with inline test JSON.

Step 4 — Automate

Add File Changed trigger to run when new files land in an inbox folder — pairs naturally with File Drop Automation.

Related tutorials

Nodlyn Assistant
Ask me anything about Nodlyn
Hi! 👋 I'm the Nodlyn assistant. Ask me about the product, workflow components, connectors, agent runtime, agent capabilities, deployment, and more. If I don't know an answer, I'll point you to our contact form.