Logic & Automation (ETL)
      Back to home
      1. Home
      2. 5: Automation & Workflows
      3. Logic & Automation (ETL)

      Data Summary Node Configuration Guide

      The Data Summary Node is used to consolidate multiple data points into a single payload over a defined time window. It simplifies and summarizes incoming data streams, allowing users to extract meaningful insights, identify trends and more..

      What Is the Data Summary Node?

      The Data Summary Node is designed to collect and group data over a specified interval or category (e.g., per device) and generate a single summarized output. This is useful for transforming high-frequency or high-volume data into concise, analyzable datasets that reflect aggregated values like averages, totals, minimums, and maximums.

      This node is ideal for:

      • Aggregating high-frequency data into structured summaries suitable for downstream analysis and visualization

      • Extracting time-based metrics such as averages, counts, and extrema across defined intervals

      • Transforming raw event streams into compressed, meaningful datasets for dashboards, alerts, and reporting

      • Improving processing efficiency by minimizing payload size and computation frequency in workflows and data exports

       Step-by-Step: How to Configure the Data Summary Node

      1. Add the node

        • Drag the Data Summary Node from the Logic section to your canvas.

      2. Connect the input data

        • Link one or more upstream workflow nodes that emit the values to be summarized.

      3. Open configuration

        • Double-click the node to access its configuration window.

       General Configuration

      Field Requirement Description
      Node Name* Required A label to identify this node (e.g., 5 Min Summary by UID).
      Calculation Interval* Required Defines how long the node collects data before producing a summary (e.g., 5 minutes).
      Output Delay (minutes) Optional Adds a delay to wait before outputting the summarized payload.
      Time Zone Setting Optional Choose whether the timestamp is interpreted in UID time zone or system default.
      Additional Delay Between Outputs (ms) Optional Inserts a time gap (in milliseconds) between multiple payloads for throttling.
       

       Field-Level Configuration

      Each field you wish to summarize must be configured with the following:

      Field Requirement Description
      JSON Key* Required The name of the field in the incoming JSON to be summarized.
      Calculation* Required Choose from:
      Average, Sum, Min, Max, Count, First, Last.
      Output JSON Key* Required Name of the key used in the output payload to store the result.
      Nested JSON Objects Optional Set to Yes if the target field is inside a nested object.
      Apply To* Required Choose how to group the summary:
      – UID (per device)
      – Label
      – All
       

      ➕ Add additional fields to process multiple summaries in one payload.

       Output Example

      If summarizing two fields (temperature and pressure), the output might look like:

      json
      CopyEdit
      {
      "temperature_avg": 22.4,
      "pressure_max": 1021
      }

      Each key is determined by your Output JSON Key for each configured field.

       Best Practices

      • Align the calculation interval with the expected data frequency (e.g., 5 minutes for sensor telemetry, 1 hour for batch logs).

      • Use UID grouping to generate per-device summaries, or All to aggregate across all incoming data.

      • Define clear and descriptive output field names (e.g., temperature_avg, power_sum) for downstream use in dashboards or exports.

      • Use the Output Delay setting to account for late-arriving data or synchronize with reporting cycles.

      • Enable Nested JSON Objects only when target fields reside within sub-structures of the payload.

      • Apply the node to consolidate high-frequency event streams into lower-frequency, structured summary payloads that are more efficient to store, transmit, and analyze.

       


       Use Cases

      • Summarize average environmental conditions every 15 minutes

      • Count data transmissions per device per hour

      • Find the maximum energy usage per label group daily

      • Create clean time-based records for dashboard or export

       Frequently Asked Questions (FAQ)

      Q: Can I output multiple summaries at once?

      A: Yes. You can define multiple fields within the same node, each with its own calculation type and output key.

      Q: How does grouping work with labels?

      A: If you’ve defined Device Labels in your Workspace, you can group summaries by label instead of UID.

      Q: Is this node passive or does it emit outputs on schedule?

      A: It emits on interval, meaning it outputs one payload per group every time the interval elapses.