Every Data Received

The Every Data Received trigger starts a workflow every time a device sends data. Unlike the Datastream Change trigger, this fires on every single data point regardless of whether the value changed.

Overview

The Every Data Received trigger is ideal for real-time processing of all incoming device data.

How It Works

1. Select the device and datastream(s) to monitor
2. The workflow starts on every data point received
3. The data is passed to the workflow for processing

Configuration

Use Cases

• Real-time processing — Process every data point as it arrives
• Data forwarding — Forward all device data to external systems
• Immediate logging — Log every data point to an external database
• Live dashboards — Update dashboards with the latest data

Example: Data Forwarding

Trigger: Every Data Received
  Device: "Sensor Array A"
  Datastream: All

→ Workflow formats the data
→ Workflow sends via HTTP Request to external API
→ Workflow confirms receipt

Important Considerations

High Volume

This trigger fires on every data point, which can mean thousands of executions per day:

• Monitor your workflow execution count
• Be aware of rate limits and concurrency limits
• Consider using Datastream Change if you only need changes

When to Use This vs Datastream Change

Tips

• Use conditions to filter out unnecessary executions
• Combine with data nodes to transform data before forwarding
• Monitor execution logs to ensure the workflow is performing well

Next Steps

Connect the trigger to action nodes like HTTP Request or MQTT Publish to forward data, or to data nodes for processing and storage.