Pass Through Node
Logic Technical Deep Dive
The Pass Through Node is a fundamental logic component designed to enhance workflow structure and manageability without performing any data processing or transformation. This document details its technical specifications, including purpose, how it works, configuration schema, input/output data formats, and error handling.
Purpose and How the Node Works
The Pass Through node serves as a placeholder or transition point in a workflow. It does not execute any processing or transformation logic; instead, it simply passes the input it receives directly to the output. Workflow designers use this node to improve structure, clarity, and manageability of complex workflows, particularly for merging divergent execution paths.
Input Resolution:
$input: It receives the aggregated output from all preceding nodes that transition into it.
$secret: While $secret can be referenced in other node types, the Pass Through Node does not inherently use secrets for its core functionality.
Request/Processing:
The node does not modify or transform the input data in any way.
It returns the received input as-is.
Execution Model: Blocking – the node completes its operation (passing data) before the workflow proceeds.
Response Handling:
Success: The input is returned as the output. No transformation or validation is performed.
Failure: Failure is highly unlikely for this node, as it performs no complex logic. Any internal system error would result in a 500-level response.
Configuration Schema
The Pass Through Node has a minimal configuration, primarily for documentation within the workflow builder.
Field
Type
Required
Description
name
string
No
Optional name for the Pass Through Node.
description
string
No
Optional description for the Pass Through Node.
Output Schema
The output schema of this node is dynamic and mirrors the schema of the input it receives. The Pass Through node does not modify or transform the input data in any way, ensuring the output is an exact copy.
Examples
Success Example
Configuration:
JSON
{
"name": "Merge Property Details",
"description": "Combines details from different property collection paths."
}
Input (from previous nodes):
JSON
{
"propertyType": "Residential",
"address": "123 Main St",
"ownerDetails": {
"name": "Jane Doe",
"contact": "[email protected]"
}
}
Output:
JSON
{
"propertyType": "Residential",
"address": "123 Main St",
"ownerDetails": {
"name": "Jane Doe",
"contact": "[email protected]"
}
}
Single-Node Test API
For testing a node in isolation (e.g., via the UI "Test" button or a dedicated API), the following endpoint is used:
Path: /skill-runtime/workflows/nodes/PassThrough/execute
Method: POST
Purpose: Execute one node in isolation.
Request Body:
JSON
{
"config": {
"name": "Placeholder Node",
"description": "For better workflow structure"
},
"input": {
"userId": 12345,
"status": "active"
}
}
Error Handling
500 Internal Server Error: Occurs due to an unexpected runtime failure within the node's execution environment.
Note: Missing input or misconfigurations are not considered errors for this node, as it's designed to simply pass through whatever it receives.
Security Notes
Does not use $secret variables for its core functionality.
Input/output is not redacted. Ensure no sensitive data is passed through the Pass Through Node unless explicitly intended and handled by other security-focused nodes (e.g., PII Guard) either upstream or downstream.
Data is processed in-memory and not persisted by the node itself.
Last updated