How data enters and exits Rayven workflows: Push and Pull explained
Overview
Rayven supports both Push and Pull mechanisms for integrating with external systems. These terms refer not just to Rayven sending data out or bringing data in, but also to how data is retrieved from or pushed into Rayven.
Understanding the distinction is important when configuring connector and output nodes, designing workflows, or integrating third-party systems via API, FTP, MQTT, or other protocols.
What is Push vs Pull in Rayven?
Rayven supports four scenarios using two directional concepts:
| Direction | Mechanism | Description |
|---|---|---|
| Into Rayven | Push | External systems push data into Rayven (e.g., via HTTP webhook, Connector, MQTT etc). |
| Into Rayven | Pull | Rayven pulls data from an external system (e.g., via API, Connector etc). |
| Out of Rayven | Push | Rayven pushes data out to external systems (e.g., via Output to HTTP, Output to MQTT, etc.). |
| Out of Rayven | Pull | External systems pull data from Rayven by querying its API endpoints configured via Output to API nodes. |
Examples of Push and Pull Mechanisms
Push into Rayven
- A third-party platform posts data to a Rayven HTTP connector endpoint (e.g., webhook).
-
An external sensor sends telemetry data to Rayven via MQTT.
Pull into Rayven
-
Rayven uses the API node to periodically fetch data from an external system via a GET request.
-
Rayven uses a product-specific connector node e.g. Google Sheets to retrieve a file for ingestion.
Push out of Rayven
-
A workflow uses an Output to HTTP node to send data to a webhook URL.
-
Rayven pushes a payload to a Modbus control system or publishes to an MQTT broker.
Pull out of Rayven
-
An external dashboard queries Rayven’s Output to API endpoint to fetch processed metrics.
-
A third-party system polls an FTP folder that is populated by Rayven's Output to FTP node.
Choosing the Right Pattern
| Use Case | Mechanism | Example |
|---|---|---|
| A sensor sends updates to Rayven in real time | Push to Rayven | MQTT connector receives data |
| Rayven polls an ERP system for updates | Pull into Rayven | API node requests data via a GET request |
| Send alerts to external control system when thresholds are crossed | Push from Rayven | Output to HTTP, MQTT, Email |
| External BI tool retrieves latest calculated metrics | Pull from Rayven | Calls Output to API node endpoint |
Summary
Rayven enables full integration flexibility through both Push and Pull mechanisms in both directions—into and out of the platform. Use Push when data is actively sent to or from Rayven. Use Pull when Rayven or an external system is querying or requesting data.
Choosing the right mechanism is a core design decision when building effective workflows and external integrations.
FAQs
What is Push in Rayven?
Push refers to when data is sent into Rayven (e.g., via HTTP connector or MQTT) or sent out from Rayven to another system (e.g., Output to HTTP, MQTT, or Email).
What is Pull in Rayven?
Pull refers to when Rayven retrieves data from external systems (e.g., using the API node or product-specific connector), or when external systems retrieve data from Rayven by querying Output to API or polling an FTP output.
Can I use both Push and Pull in a single workflow?
Yes. For example, Rayven can pull data from an external API, process it, push the result to a third-party system, and simultaneously expose the result via Output to API for external pull.
Does Rayven support real-time Push data?
Yes. Connector nodes like MQTT and HTTP can receive real-time data pushed into Rayven, immediately triggering workflows.
Is Output to API a Push or Pull mechanism?
It’s a Pull from Rayven mechanism. External systems call the configured endpoint to retrieve data on demand.