Portal Community

Relationship to ExecutionMemory

When an executor returns NodeExecutionResult.Success(output: myData), the Process Engine stores myData under ExecutionMemory.nodeOutputs[nodeId]. The Node Inspector's Output Data section reads directly from this.

// Backend: how output is produced
return NodeExecutionResult.Success(output: new {
  statusCode = (int)response.StatusCode,
  body = await response.Content.ReadAsStringAsync(),
  headers = response.Headers.ToDictionary(h => h.Key, h => h.Value)
});

// Frontend: this output appears under $output.{nodeId}
// In the inspector, the Output Data JSON tree shows:
{
  "statusCode": 200,
  "body": "{\"id\":42,\"name\":\"Acme Corp\"}",
  "headers": { "Content-Type": ["application/json"] }
}

Output Availability

Node StatusOutput Data
pending / runningnull — not yet produced
completedFull output object from NodeExecutionResult.Success
failednull — executor did not complete
skippednull — executor was not run

Copy Output as JSON

A "Copy JSON" button at the top of the Output Data section copies the entire output to the clipboard as a formatted JSON string. This is useful for: