Input Data Section

What "Input Data" Means

Each node has one or more input ports defined in its ProcessElementPort configuration. When the Process Engine executes a node, it resolves the input for each port from ExecutionMemory — this resolved data is what appears in the Input Data section.

For a typical node with one main input port, the input data is the output of the immediately preceding node (or the trigger data for the first node).

Example

// Input data for an HTTP Request node
{
  "main": {
    "customerId": 42,
    "tier": "gold",
    "requestedAt": "2026-05-25T14:03:20Z"
  }
}

// The "main" key corresponds to the node's main input port key
// Nodes with multiple input ports will have one key per port

Multi-Port Nodes

Nodes with multiple input ports show data for each port separately:

// Input data for a Merge node with two input ports
{
  "left": {
    "customerData": { "id": 42, "name": "Acme Corp" }
  },
  "right": {
    "invoiceData": { "invoiceId": "INV-2026-001", "amount": 5000 }
  }
}

Why Input Data Matters for Debugging

• A node failed with "field not found" — check if the required field was actually present in the input
• A condition node took the wrong branch — read exactly what value the condition received and evaluated
• A transform node produced wrong output — verify the transformation was applied to the correct input