In Rayven.io, data triggers are a key component of real-time data management, allowing workflows to automatically respond to data changes or conditions.
Data triggers in Rayven.io enable real-time, rule-based automation within workflows. By defining conditions or schedules, you can automatically initiate processes, alerts, or external integrations when specific data events occur or on a recurring basis.
What Is Triggering Data?
In Rayven.io, triggering data refers to initiating an action or workflow automatically based on:
-
A specific data condition (e.g., value exceeds threshold)
-
A time-based schedule (e.g., every 10 seconds, once per day)
This capability is critical in real-time environments where immediate action or routine automation is required.
Trigger Types in Rayven.io
1. Condition-Based Triggers
These respond to real-time data values. Examples:
-
Temperature > 75°C
-
Vibration spike detected
-
Device status = “Offline”
2. Time-Based Triggers
You can configure Rayven workflows to trigger:
-
At specific intervals (e.g., every 10 seconds, every 5 minutes)
-
At specific times (e.g., daily at midnight, every Monday at 8 a.m.)
These time-based triggers are useful for:
-
Periodic reports
-
Batch processing
-
Scheduled data exports
-
Regular system checks
You configure this logic within input nodes or workflow scheduling settings.
How Data Triggers Work in Workflows
Workflows in Rayven consist of a sequence of nodes for data ingestion, logic, and action. Triggers are embedded into these workflows via logic or schedule settings.
Key Components
| Component | Description |
|---|---|
| Input Nodes | Ingest real-time or scheduled data |
| Logic Nodes | Define trigger conditions (e.g., temperature > 75°C) |
| Schedule Config | Set time-based execution intervals or triggers |
| Action Nodes | Define what to do when a trigger fires (e.g., send alert, export data) |
Configuring Triggers in a Workflow
Step 1: Ingest Data
-
Use Input Nodes for streaming (real-time) or scheduled inputs (batch)
-
For time-based triggers without external data, use internal scheduler nodes
Step 2: Define Trigger Logic
-
Condition-based: Use Rule Builder or Function Nodes to apply logical conditions
-
Time-based: Use scheduling options to trigger workflows:
-
At regular intervals (e.g., every 10 seconds)
-
On recurring schedules (e.g., every 24 hours)
-
At exact times (e.g., “03:00 AM daily”)
-
Step 3: Specify Trigger Actions
-
Send an alert (Email, SMS)
-
Launch another workflow
-
Control external systems
-
Export data to a database or third-party platform
Example Use Cases
Scheduled Report Workflow
-
Trigger Type: Time-based (daily at 6 AM)
-
Action: Aggregate energy usage data and email a report to stakeholders
Real-Time Fault Detection
-
Trigger Type: Condition-based (vibration > threshold)
-
Action: Alert maintenance and initiate diagnostic process
Regular System Sync
-
Trigger Type: Every 10 seconds
-
Action: Pull data from a third-party API and update Rayven’s tables
Benefits of Triggering in Rayven
| Benefit | Description |
|---|---|
| Automation | Remove manual intervention from critical processes |
| Flexibility | Support both event-driven and scheduled triggers |
| Real-Time Response | Act immediately on abnormal conditions or sensor readings |
| Routine Management | Handle recurring jobs like exports, health checks, or daily reports |
Frequently Asked Questions
Q: Can Rayven trigger workflows on a timer (e.g., every 10 seconds)?
Yes. You can configure input nodes or schedule settings to execute workflows at fixed intervals, such as every 10 seconds, every 5 minutes, or hourly.
Q: Can I trigger a workflow only once per day?
Yes. Time-based triggers can be set for once-daily execution (e.g., every day at 08:00), suitable for reporting, maintenance, or batch exports.
Q: Can I combine time-based and condition-based triggers in the same workflow?
Yes. You can set workflows to run on a schedule and still include logic that filters or evaluates incoming data before taking action.
Q: Can I control external devices using Rayven triggers?
Yes. Triggers can activate control nodes that send commands to external systems, APIs, or connected IoT devices.
Q: Do time-based triggers work if no data is received?
Yes. Time-based triggers execute regardless of data input. You can design workflows to run independent of live data streams.
Q: How do I test a scheduled trigger before deployment?
You can manually execute the workflow or temporarily adjust the schedule (e.g., trigger every 1 minute) to verify behavior in development.
Summary
Rayven.io supports both data condition triggers and time-based triggers in its low-code workflow environment. Whether you're building real-time alert systems or scheduled reporting pipelines, triggers give you the control to automate processes with precision.
Would you like a set of prebuilt workflow templates that demonstrate different trigger types? I can prepare examples for alerting, scheduled exports, and control loops.