Output Connector Nodes
      Back to home
      1. Home
      2. 5: Automation & Workflows
      3. Output Connector Nodes

      Output to HTTP (Webhook) Node Configuration Guide

      The Output to HTTP (Webhook) Node allows you to send JSON-formatted payloads from your Rayven workflow to a remote HTTP endpoint using an HTTP POST request. This node is commonly used to forward data to third-party systems, trigger external workflows

      What It Does

      Each time this node receives a payload, it serializes the payload and posts it to the specified external URL. The request is sent using HTTP/1.1 POST with a Content-Type: application/json header (or other formats if supported in future).

      Step-by-Step: How to Configure the Node

      1. Add the node

        • Drag the Output to HTTP (Webhook) node from the Outputs section to the canvas.

      2. Connect upstream nodes

        • Link this node to the part of the workflow where payloads should be forwarded externally.

      3. Open configuration panel

        • Double-click the node to define the destination endpoint and output format.

      4. Activate the node

        • Click Activate, then Save.

      Configuration Fields

      Field Requirement Description
      Node Name* Required Name for the node as it appears in the workflow.
      Destination (POST) Endpoint* Required Full URL to which data will be posted (e.g., https://example.com/webhook). Must accept POST.
      Output Format Required Format for the payload. Currently supported: JSON.
       

      Output Payload Structure

      The full payload received by this node is serialized and sent as the body of the HTTP POST request.

      Example:

      Input to node:

      json
      CopyEdit
      {
      "uid": "device-01",
      "temperature": 72.5,
      "status": "active"
      }

      POST Request:

      bash
      CopyEdit
      POST https://example.com/webhook
      Content-Type: application/json

      {
      "uid": "device-01",
      "temperature": 72.5,
      "status": "active"
      }

      Security Considerations

      • This node does not include authentication headers by default. If your endpoint requires API keys or tokens, consider using an intermediary or reverse proxy.

      • Always use HTTPS endpoints for secure data transmission.

      Best Practices

      • Confirm that the destination system is reachable and accepting JSON POST requests before activating the node.

      • Use tools like RequestBin or Postman to test webhooks during development.

      • If retry logic or response handling is required, implement it at the receiving endpoint — this node sends and moves on.

      Use Cases

      • Forward device events to a third-party alerting system

      • Send summarized data to a remote dashboard or reporting service

      • Trigger a cloud function or API when a rule condition is met

      • Integrate with CRMs, ERPs, or cloud-based automation platforms (e.g., Zapier, Integromat)

       FAQ

      Q: Can this node send custom headers?

      A: Not currently. It uses Content-Type: application/json and does not support custom header injection.

      Q: Can it retry on failure?

      A: No. Delivery is best-effort — no built-in retry or response evaluation. Use buffering upstream if reliability is critical.

      Q: Does the endpoint need to return a specific status code?

      A: No. The node does not depend on the response body or status code. However, a 2xx response is expected to confirm delivery.