8: How-to Guides
      Back to home
      1. Home
      2. 8: How-to Guides

      How to Create Real-Time Workflows Using Linked Tables in Rayven.io

      Real-time workflows in Rayven.io allow you to instantly react to data events — like new records, updates, or incoming streams.

      Overview

      By linking Primary and Secondary Tables, you can trigger complex, relational logic the moment data changes, enabling automated decisions, alerts, and actions without delay.

      This is key for live monitoring, reactive automation, and any use case where speed matters.

      Use Cases

      • Instantly send an alert when a sensor value crosses a threshold, using metadata from the device’s primary table.

      • Automatically log a maintenance request when a status update is posted to a secondary table.

      • Trigger a generative AI summary when multiple linked data conditions are met in real time.

      • Push live insights to a dashboard when new events are received.

      How It Works

      Real-time workflows are triggered by event-based nodes like:

      • New row added

      • Data updated

      • Stream received

      From there, you can:

      • Pull in linked data from another table

      • Join datasets using a common key (e.g., device_id)

      • Perform logic checks and act instantly

      Step-by-Step Instructions

      Step 1: Start a New Workflow

      1. Go to Workflow Builder.

      2. Click + Create Workflow → Give it a name like Live Device Alerts.

      Step 2: Add a Real-Time Trigger

      Choose a trigger node based on your use case:

      • New Row in Table → For new records (e.g., Sensor Readings)

      • Data Updated → For status changes

      • Streaming Input → For MQTT or other data streams

      Step 3: Pull Related Data

      1. Drag in a Table Lookup Node or another Table Data Node.

      2. Use the incoming record’s field (e.g., device_id) to:

        • Look up the related Primary Table (e.g., Devices)

        • Bring in fields like location, type, or assigned_operator

      Step 4: Add Business Logic

      • Use Condition Nodes to apply logic (e.g., if temperature > 80°C AND device_type == 'compressor').

      • Use AI Agent Nodes to generate smart summaries.

      • Use Math or Logic Nodes to calculate or transform values.

      Step 5: Add Output Actions

      Examples:

      • 📧 Send Notification (to user or operator)

      • 🧠 Trigger Generative AI (for auto response or report)

      • 🛠️ Create new row in another table (e.g., log or job table)

      • 🌐 Push to API or external system

      Step 6: Save and Activate

      • Test the workflow using real or sample data.

      • Use Logs to verify input/output accuracy.

      • Set the workflow status to Active.

      Best Practices

      • Use stable keys (like device_id) for linking to avoid data mismatches.

      • Log real-time outcomes to a secondary “event log” table for traceability.

      • Handle edge cases (missing fields, null lookups) with fallback logic.

      • Avoid overly complex joins in high-frequency flows — keep it lean and reactive.

      Examples

      Trigger Primary Table Linked Table Real-Time Outcome
      New sensor reading Devices Sensor Logs Alert if out of range
      Status change Equipment Maintenance Logs Auto-create job
      Live stream Machines Operators AI alert with context

      Troubleshooting

      • Workflow not triggering?
        Ensure your real-time trigger is connected to the correct table or data source.

      • Missing linked data?
        Check that the incoming record includes the correct join field (e.g., device_id exists in both tables).

      • Unexpected output?
        Use a Logger Node or Log Table to inspect values at each step.

      Next Steps

      👉 How to Link Tables in Workflows
      👉 How to Set Up Real-Time Notifications
      👉 Using AI Agents in Real-Time Flows
      👉 Monitoring Workflow Performance