Data Inspector icon

Data Inspector

Inspect and analyze workflow data structure

Extract Keys

AI-generated

Overview

The Data Inspector node analyzes and inspects the structure and content of workflow data items. It supports operations such as analyzing the data structure, counting items and properties, extracting all unique keys, and summarizing data types. This node is useful for understanding the shape and characteristics of data passing through a workflow, which helps in debugging, data validation, and designing subsequent processing steps.

Use Case Examples

  1. Extract all unique keys from incoming data items to identify all possible fields present.
  2. Count the total number of items and properties to get an overview of data volume and complexity.
  3. Summarize data types of properties to detect inconsistencies or unexpected types in the data.

Properties

Name Meaning
Operation Specifies the type of data inspection to perform. Options include Analyze Structure, Count Items, Extract Keys, and Type Summary.

Output

JSON

  • totalItems - Total number of input data items.
  • structure - Array describing each item's index, properties, property count, and types (only for Analyze Structure operation).
  • totalProperties - Total count of all properties across all items (only for Count Items operation).
  • averagePropertiesPerItem - Average number of properties per item (only for Count Items operation).
  • uniqueKeys - Sorted array of all unique keys found in the data (only for Extract Keys operation).
  • totalUniqueKeys - Count of unique keys found (only for Extract Keys operation).
  • keyFrequency - Object mapping each key to the number of items containing that key (only for Extract Keys operation).
  • propertyTypes - Object mapping each property to counts of detected data types (only for Type Summary operation).
  • summary - Array summarizing dominant type and type distribution for each property (only for Type Summary operation).

Troubleshooting

  • Ensure input data is properly formatted JSON objects; otherwise, keys and types may not be extracted correctly.
  • If no data items are provided, outputs will reflect zero counts or empty arrays.
  • Large datasets may cause performance delays during key extraction or type summarization due to iteration over all items.

Discussion