Ruvix

Key Concepts ​

Before building your first workflow, here are the core concepts you'll encounter throughout the platform.

Workflows ​

A workflow is a visual graph of connected nodes that defines an automated process. Each workflow starts with a trigger node and can contain any number of processing nodes connected by edges.

Workflows are executed as a DAG (directed acyclic graph) — nodes run in dependency order, and independent branches run in parallel automatically.

Nodes ​

A node is a single unit of work in your workflow. Each node has a specific type that determines what it does:

  • Trigger nodes start a workflow (manual, webhook, cron schedule, or DataStore change)
  • Core nodes process and transform data (Transform, Switch, Merge, HTTP Request, etc.)
  • Database nodes read from and write to external databases (MySQL, PostgreSQL, Supabase)
  • DataStore nodes interact with your built-in database
  • File transfer nodes read and write files on remote SFTP servers
  • Redis nodes perform key-value operations on Redis

Edges ​

Edges are the connections drawn between nodes that define how data flows. An edge connects an output handle on one node to an input handle on another.

Some nodes have multiple output handles for conditional routing. For example, a Switch node routes data to different paths based on conditions.

Connections ​

A connection stores encrypted credentials for an external service — a database host, SFTP server, or Redis instance. Nodes that interact with external services require a connection to be configured.

Connections are shared across all workflows in your team.

Executions ​

An execution is a single run of a workflow. When a workflow is triggered, an execution is created that tracks the status and output of every node.

Executions can be:

  • Completed — all nodes finished successfully
  • Failed — one or more nodes encountered errors
  • Partial success — some nodes succeeded while others failed
  • Paused — execution was manually paused and can be resumed

Versions ​

Workflows support versioning with two key states:

  • Working version — your current draft that you're editing
  • Published version — the version that runs when triggered by webhooks or cron schedules

You can view version history, compare versions, and restore previous versions as needed.

Teams ​

Every account belongs to a team. Teams provide:

  • Isolated data — each team has its own database, workflows, and connections
  • Role-based access — Admin, Editor, and Viewer roles control who can do what
  • Usage limits — daily execution limits and concurrent run limits based on your plan