The Send Data to Node node enables one Rayven workflow to transmit data directly to another node in a different workflow. This facilitates inter-workflow communication and supports modular architecture.
What It Does
This node takes the current payload from a workflow and sends it to a specific node in another workflow, using internal referencing by workflow and node IDs. It effectively acts as a handoff, allowing complex logic to be split across multiple reusable workflows.
No transformation occurs during the handoff—payloads are passed as-is.
Step-by-Step: How to Configure the Send Data to Node Node
1. Add the node
Drag the Send Data to Node node onto the canvas.
2. Name the node
Give it a clear label (e.g., "Forward to Alert Dispatcher").
3. Set destination workflow ID
Enter the Workflow ID of the target workflow that will receive the payload. You can find this in the workflow’s settings or URL.
4. Set destination node ID
Enter the Node ID of the specific node within the destination workflow that should receive the data. This is usually the entry point node (e.g., a rule engine, logger, or output node).
Configuration Fields
| Field | Requirement | Description |
|---|---|---|
| Node Name* | Required | Label for this node in the canvas. |
| Destination Workflow ID* | Required | The ID of the target workflow receiving the data. |
| Destination Node ID* | Required | The ID of the target node within the destination workflow. |
Example: Forward Alert Payload to a Notification Workflow
Use Case: A temperature processing workflow detects threshold breaches. Instead of sending notifications directly, it offloads this task to a shared alert workflow.
Configuration:
-
Node Name:
Forward Alert Payload -
Destination Workflow ID:
wf_5f2313abc9e3a -
Destination Node ID:
nd_b31a65fd9d1f4
Result:
When triggered, this node sends the current payload to the specified node in the target workflow, enabling centralized alert handling.
Best Practices
-
Use this node to decouple workflows and promote modular design.
-
Ensure the receiving workflow is published and designed to accept the payload structure.
-
If multiple entry points exist in the destination workflow, route to the correct node ID based on logic purpose (e.g., export, log, transform).
-
Keep a documented map of workflow and node IDs for easier maintenance.
Use Cases
-
Send processed sensor data from edge workflows to a master workflow for analytics.
-
Trigger alerting or messaging logic from any workflow by routing to a shared handler.
-
Push payloads to a workflow that handles exports, backups, or integrations.
-
Chain workflows to break down complex logic into manageable units.
FAQ
Q: Does the destination workflow need to be running?
A: Yes. The target workflow must be active and published; otherwise, data transfer may silently fail.
Q: Can I send data to multiple workflows from the same node?
A: No. Each Send Data to Node instance targets a single destination. To send to multiple workflows, use multiple nodes.
Q: Does the payload change during the transfer?
A: No. The payload is passed through exactly as received—no transformation or wrapping occurs.
Q: Can I send data from event-based or scheduled triggers?
A: Yes. This node works with all upstream triggers—event, scheduled, or manual.