Output Inspector
Captures and displays inspected values in the Output console window
Overview
Terminal sink node that captures any incoming value (Bytes, String, Int, Bool, or Set), logs a human-readable summary to the Output console window, and renders the live result directly on the canvas card.
For Bytes values, the card displays both the byte length and the hexadecimal preview; for String, Int, and Bool values, it displays the formatted value directly.
When to Use
- Inspecting final or intermediate ciphertexts, plaintext recoveries, hashes, signatures, or boolean verification results right on the canvas.
- Attaching multiple labeled inspectors at different stages of a cryptographic pipeline (e.g., after padding, after encryption, and after unpadding) to compare intermediate states.
Parameter Configuration
Output Inspector has no algorithm parameters in propertySchema. You can customize the node's Label / Title in the inspector header to label the output entry in the console and on the canvas card.
Port I/O Specification
See Ports & Connections for general wiring rules, data type colors, and dynamic port creation.
Input Ports
Port Nature: Fixed Input Ports (1 total).
| Port Name | Port ID | Data Type | Required | Visibility Condition | Description |
|---|---|---|---|---|---|
In |
data |
Any |
Required | Always visible | Accepts data of any type (any) to capture, log, and display. |
Output Ports
This node has no output ports.
Error Cases
This node has no runtime failure cases (errorProfile: none) and always succeeds for any valid typed input.
Examples
Inspecting Ciphertext and Authentication Tag
Attach two Output Inspector nodes to an AES-GCM Encrypt node.
- Connect the
Ciphertextoutput of AES Encrypt to one Output Inspector (labeledCiphertext). - Connect the
Auth Tagoutput to a second Output Inspector (labeledGCM Tag) and run the workflow.