Overview
This node, named "Collector," is designed to aggregate and process information about assets. It collects input data, optionally filters out previously memorized data, and then processes the remaining data through a series of connected runner nodes in order of priority. The processed results are collected and output as JSON.
Common scenarios where this node would be beneficial include:
- Aggregating and updating asset information from multiple sources.
- Filtering out already processed or memorized data to avoid duplication.
- Running a sequence of processing steps (executors and runners) on asset data to enrich or transform it.
For example, you might use this node to collect asset details from an input stream, ignore assets that have been processed before (memorized), run them through various enrichment steps (runners), and output the final enriched asset data.
Properties
| Name | Meaning |
|---|---|
| Asset | A JSON object representing the asset data to be collected and processed. |
| Ignore Memorized Data | Boolean flag indicating whether to skip using previously memorized data during processing. |
Output
The node outputs an array of JSON objects under the json field. Each object represents a processed asset, potentially enriched or filtered based on the logic of connected executor and runner nodes.
If binary data is present in the input, it is preserved and passed along with the JSON data.
Dependencies
This node depends on connections to other nodes of specific types:
- Executor: Required connection that provides execution logic for processing assets.
- Memorizer: Optional connection used to load and save memorized data to filter duplicates.
- Runner(s): Optional one or more connections that run additional processing steps on the asset data, executed in priority order.
No external API keys or services are directly required by this node itself; however, the connected executor, memorizer, and runner nodes may require their own credentials or configurations.
Troubleshooting
Issue: No output or incomplete output.
- Cause: Missing or misconfigured Executor or Runner connections.
- Resolution: Ensure that at least one Executor node is connected and properly configured. Verify Runner nodes if used.
Issue: Memorized data not being ignored when expected.
- Cause: The "Ignore Memorized Data" property is set to false.
- Resolution: Set "Ignore Memorized Data" to true to bypass filtering of memorized data.
Issue: Errors related to input data format.
- Cause: The "Asset" property expects valid JSON input.
- Resolution: Validate the JSON structure of the asset data before passing it to the node.