Low Code Workflow Programming

The Rayven Drag-and-Drop Workflow Builder offers an intuitive, low-code environment that simplifies the creation of data workflows, allowing users to connect systems, automate processes, and visualize results—all without needing to write code.

 

Workflow1

What Is the Rayven Workflow Builder?

The Rayven Workflow Builder is a visual interface designed to help users create complex workflows using a drag-and-drop approach. Each workflow is built by connecting modular components called nodes. These nodes represent actions such as data ingestion, transformation, filtering, logic application, and output.

This builder is designed for users of all skill levels—allowing both non-technical users and developers to configure workflows efficiently.


Key Features

1. No-Code / Low-Code Environment

Most tasks can be completed without writing code. Users define behavior by configuring node settings through visual menus instead of programming logic manually.

2. Nodes as Building Blocks

Workflows are made up of nodes, each performing a specific function:

  • Input Nodes: Ingest data from sources like APIs, devices, or databases

  • Processing/Logic Nodes: Apply transformations, filters, and business rules

  • Output Nodes: Send results to external systems, dashboards, or notifications

3. Custom Logic Without Coding

Users can:

  • Set up conditional logic

  • Define data transformations

  • Trigger actions based on thresholds or rules
    All through a visual interface, without writing code.


How the Drag-and-Drop Workflow Builder Works

Step 1: Create a Workflow

  • Navigate to the Workflows section

  • Click Create a Workflow

  • A blank canvas appears where nodes can be added and connected

Step 2: Add and Connect Nodes

Drag nodes from the palette onto the canvas. Nodes are categorized:

  • Input Nodes: Data sources (e.g., API, sensor, file upload)

  • Logic Nodes: Filter, map, calculate, route, or evaluate data

  • Output Nodes: Dashboards, emails, databases, or third-party services

Example:

  • Drag an API Input Node to fetch temperature data

  • Connect it to a Function Node to check for high values

  • Connect that to an Email Node to notify users if a threshold is exceeded

Step 3: Configure Node Settings

Each node has a configuration panel where you:

  • Set field mappings

  • Define logic and thresholds

  • Choose output formats

  • Configure connectors or endpoints

Step 4: Define Conditional Logic

Use logic nodes to build decision trees without writing if/else statements:

  • Route data to different branches based on value conditions

  • Trigger alerts only if conditions are met

  • Combine multiple rules using visual filters

Step 5: Test and Debug

Rayven includes debugging tools such as Debug Nodes:

  • Capture data flowing through the workflow

  • View intermediate results

  • Validate node logic and output structure

Step 6: Save and Deploy

Once tested, save and activate your workflow. It will begin processing live or scheduled data, triggering outputs, and updating dashboards in real-time.


Low-Code Programming in Rayven

Visual Logic Configuration

Users apply business logic by selecting from pre-defined options in a node’s configuration panel. Filtering, mapping, and rule application are all handled visually.

Pre-Built Nodes

Rayven provides over 60 ready-made nodes for:

  • Data ingestion

  • API calls

  • Data processing

  • Alerting and output
    These nodes can be reused and configured as needed.

Conditional Logic Without Code

The workflow engine supports branching logic visually:

  • Route data based on labels or thresholds

  • Apply multi-step logic flows

  • Define fallback actions or alerts

Customizable Functionality

Advanced users can add JavaScript to Function Nodes if needed. This allows for:

  • Custom calculations

  • Complex string parsing

  • Advanced formatting

Dynamic Data Management

Use Primary Table data for SQL-style operations like:

  • Filtering by labels (e.g., building, device type)

  • Grouping and aggregation

  • Conditional joins and lookups—all without SQL scripting


Example: Temperature Monitoring Workflow

Goal: Monitor real-time temperature from sensors and alert when values exceed a threshold.

1. Ingest Data

  • Add an API Input Node to pull temperature data

2. Process Data

  • Use a Function Node to check if temperature > 30°C

3. Conditional Logic

  • Use an If/Else Node:

    • If over 30°C → route to an alert

    • If under 30°C → log it

4. Visualization

  • Add a Chart Node to display temperature trends on a dashboard

5. Output

  • Add an Email Node to notify a user of high readings

This workflow runs entirely on a drag-and-drop model, with no manual coding.


Frequently Asked Questions

Q: Do I need to write code to build workflows in Rayven?
No. Most users can build complete workflows using only the drag-and-drop interface and pre-built nodes.

Q: Can I use custom logic if needed?
Yes. JavaScript can be used in Function Nodes to add advanced logic when necessary.

Q: How do I handle different data sources?
Rayven supports a wide range of input nodes (e.g., API, SQL, MQTT, CSV) for real-time and batch data.

Q: What happens if a node fails or returns an error?
You can use debug nodes to inspect errors and build fallback branches to handle exceptions.

Q: Can workflows interact with dashboards and tables?
Yes. Workflows can write to Primary and Secondary Tables and feed data into real-time dashboards or interfaces.

Q: Do I need to write code to build workflows in Rayven?
No. Most users can build complete workflows using only the drag-and-drop interface and pre-built nodes. No coding is required for standard tasks such as filtering, transformation, alerting, or routing.

Q: Can I use custom logic if needed?
Yes. For advanced scenarios, users can insert JavaScript into Function Nodes to handle custom calculations, formatting, or logic that goes beyond the built-in configuration options.

Q: What types of data sources can I connect to in a workflow?
Rayven supports a variety of input nodes, including API endpoints, IoT devices, SQL databases, file uploads (CSV, JSON), MQTT brokers, Modbus devices, and more.

Q: Can workflows update data in Rayven tables?
Yes. Workflows can read from and write to both Primary and Secondary Tables. This allows workflows to enrich incoming data, persist results, and power dashboards or downstream processes.

Q: How do I handle different data structures from different sources?
You can use Function Nodes to normalize or transform data. For example, you can remap field names, convert formats, or restructure payloads before processing or outputting them.

Q: How do I test a workflow before going live?
Use Debug Nodes within your workflow to inspect the data flowing through each step. You can pause the workflow, review outputs, and validate your logic before deploying.

Q: Can workflows be scheduled or triggered by events?
Yes. Rayven supports scheduled workflows (e.g., every 5 minutes) and event-driven workflows (e.g., when a device sends data or an API call is received).

Q: What happens if a node fails during execution?
Rayven provides error handling and fallback options. You can route failed data to a specific path, log the issue, or send a notification when an error occurs.

Q: Is versioning or rollback available for workflows?
Workflows can be saved in different versions. Users can revert to previous versions manually, and it is good practice to clone workflows before making major changes.

Q: Can I reuse workflows or parts of workflows?
While Rayven doesn't currently support drag-and-drop modular reuse of workflow fragments, you can copy existing workflows or use standard templates to replicate common patterns.


Summary

Rayven’s Low-Code Workflow Builder gives you the ability to build robust, scalable workflows using a visual, node-based approach. It reduces development time, removes complexity, and enables users of any skill level to connect systems, apply logic, and automate outcomes—without writing code.

Would you like help drafting internal best practices for workflow naming, testing, or template reuse? Let me know and I can prepare a follow-up article.