3: Building Your First App
      Back to home
      1. Home
      2. 3: Building Your First App

      Designing a Simple Workflow

      Learn how to create your first workflow in Rayven using the Workflow Builder

      Overview

      Workflows are the core of any Rayven application. They handle data ingestion, transformation, business logic, automation, visualisation, and integrations. This guide will walk you through the process of designing a simple workflow using the Workflow Builder in the Rayven Workspace. It covers the key concepts, steps, and best practices to help you confidently build your first workflow and understand how it fits into the broader application architecture.

      What is a Workflow in Rayven?

      In Rayven, a workflow is a logical sequence of operations that can:

      • Receive and process data from external systems (using Connector nodes)

      • Perform calculations, transformations, and apply business rules

      • Visualise data on the front-end via Interface widgets

      • Trigger alerts or send data to other systems

      • Store and retrieve data from tables

      • Interact with AI services

      All workflows are created using the Workflow Builder, a drag-and-drop development environment within the Workspace.

      Each Rayven application must have at least one workflow, but can include many depending on complexity.

      Accessing the Workflow Builder

      To access and begin creating workflows:

      1. Navigate to your application in the Rayven Workspace.

      2. Select the Workflows button.

      3. Click Create New or select an existing workflow to modify.

      Key Concepts Before You Begin

      • Nodes are the building blocks of workflows. Each node performs a specific function.

      • Data flows from left to right, from input nodes through logic nodes to output or visualisation nodes.

      • Payloads are passed between nodes as JSON structures. New fields can be appended or transformed as data moves through the workflow.

      • Workflows can be iterative, meaning you can apply logic in a workflow to each row in your Primary Table or subsets defined by label filters.

      Step-by-Step: Creating a Simple Workflow

      Step 1: Add a Connector or Trigger Node

      Choose how the workflow starts:

      • Use a Trigger Node to run workflows on a schedule or based on an event.

      • Use a Connector Node (e.g. API, HTTP, FTP, etc.) to ingest data from external systems.

      • Use a UI Code Node or Form to trigger a workflow based on a user interaction e.g. form fill, button press etc.

      add api node

      Step 2: Add Function Nodes for Data Transformation

      Insert logic nodes to:

      • Filter or enrich the data

      • Apply formulas or custom calculations

      • Combine, split or route payloads

      Examples:

      • Filter Node to restrict data to specific criteria

      • Formula Node to apply calculations

      • JavaScript Node for advanced or custom logic

      Step 3: (Optional) Update or Query Tables

      If you’re writing data to structured storage:

      • Use the Update Table Node to store values in a Primary or Secondary Table.

      • Use the Query Table Node to read values for further processing.

      Step 4: Add a Frontend Node (if interface visualisation is needed)

      To display data in your App Interface, add a Frontend node such as:

      • Value Widget

      • Line Chart

      • Table

      • UI Code Node for custom widgets

      Once added, this node becomes available for selection in the Interfaces section of the Workspace.

      Step 5: (Optional) Add an Output Node

      To send data elsewhere:

      • Use Email/SMS Output Nodes for notifications

      • Use API Output Node to push data to another system

      • Use Control System Output Node for device automation

      Step 6: Test & Save Your Workflow

      • Use the Inspect Data tab to inspect payloads during execution.

      • Save and test your workflow by manually triggering or pushing data into it.

      • Once working, you can publish the workflow to run automatically.

      Best Practices for Simple Workflows

      • Start simple: Start by reading and/or writing simple data to your Primary Table, or by receiving and visualising data from an external source. Get used to how the Workflows work.

      • Use meaningful names for nodes to keep the workflow understandable.

      • Use the Inspect Data tab to frequently during build to understand what data is flowing through your nodes.

      • Store only what you need: Be deliberate about when and where you write to structured tables.

      Summary

      Creating a simple workflow in Rayven is your first step toward building a powerful, flexible application. The Workflow Builder enables you to connect to data, apply logic, visualise results, and automate actions—without writing code for most use cases. With practice, you’ll be able to build sophisticated workflows that power entire applications.

      FAQs

      What is the minimum required for a Rayven workflow?
      A workflow requires at least one node, but most useful workflows start with a Connector or Trigger node and end with either a storage, interface, or output node.

      Can I run a workflow for each row in my table?
      Yes. Use iterative workflows to apply logic per Primary Table UID or label value. This is controlled via settings in the Trigger or Connector node.

      How do I display workflow output in the interface?
      Add a Frontend node (e.g. Value, Chart, Table) in the workflow. Then, select it in the Interface section to display it as a widget.

      Is it possible to build workflows without using the front-end at all?
      Yes. Rayven supports pure backend or data-processing applications with no visual interface, ideal for ETL, integration, automation, and AI-based processing.

      What happens to the data inside a workflow?
      Data passing through the workflow is automatically stored in Rayven’s unstructured Cassandra database, tied to the Primary Table UID and node timestamp.