1. Home
  2. 8: How-to Guides

How to Use Webhooks for 3rd-Party Integrations in Rayven.io

Rayven.io enables powerful integrations with third-party platforms using Webhooks — allowing you to send real-time data, alerts, or structured payloads to external systems such as CRMs, ERPs, Slack, service desks, or custom APIs.

Use Cases

  • Push alerts or sensor events to Slack, Teams, or Discord

  • Send structured data to an external REST API (e.g., Salesforce, HubSpot, ServiceNow)

  • Post updates to customer systems when jobs or processes complete

  • Sync data to cloud platforms like Google Sheets, Firebase, AWS Lambda

  • Trigger Zapier/Make/Integromat automations from a Rayven workflow


How It Works

A Webhook Node in your workflow can:

  1. Accept data from upstream nodes (e.g., tables, AI agents, conditions)

  2. Format the payload as JSON, form-data, or raw text

  3. Push it to an external URL with optional headers and authentication

  4. Log the response for debugging or auditing


Step-by-Step Instructions

Step 1: Set Up Your Workflow

  1. Go to the Workflow Builder

  2. Add a Trigger Node (e.g., new row, real-time stream, data update)

  3. Add any logic (e.g., conditions, AI agents, or data lookups)


Step 2: Add the Webhook Node

  1. Drag in the Webhook Node after the logic or AI node

  2. Configure the following:

🛠️ Endpoint URL

Paste in the URL of the third-party service or endpoint you're posting to

🧾 Method

  • POST (common for sending data)

  • GET, PUT, or DELETE (if required)

🧱 Payload Type

  • JSON – most commonly used

  • Form Data – if posting to web forms

  • Raw Body – if the system expects plain text or custom content

🧩 Body Content

You can:

  • Insert raw JSON

  • Use dynamic fields from earlier in the workflow (e.g., {device_id}, {temperature})

  • Pass the output of an AI Agent or Merge Node

Example JSON:

json
CopyEdit
{
"device_id": "{device_id}",
"event": "{status}",
"timestamp": "{event_time}"
}

🧾 Headers (Optional)

  • Content-Type: application/json

  • Authorization: Bearer YOUR_TOKEN

  • Add any custom API keys or tokens here


Step 3: Test the Webhook

  1. Use Preview Run to simulate the flow

  2. Monitor the response in the Workflow Logs

  3. Confirm if the endpoint accepted the payload or returned an error


Step 4: Handle Webhook Responses (Optional)

If the external system returns a response (e.g., confirmation or ID), you can:

  • Log the response into a table

  • Use it as input for the next step (e.g., AI Agent, PDF generation, etc.)

  • Trigger conditional logic based on the response


Best Practices

  • Use Logger Nodes before and after the Webhook Node for debugging

  • Always validate field values and sanitize input

  • Use throttling or batching when sending large volumes

  • Add retry logic or fallback for critical external requests

  • Keep sensitive tokens in Rayven’s secure variable storage (if supported)


Examples

Integration Use Case Payload Example
Slack Alert operator in channel { "text": "Device A1 exceeded threshold at 4:22PM." }
HubSpot Send form submission { "email": "{user_email}", "event": "form_submitted" }
ServiceNow Open ticket for incident { "short_description": "Sensor failure", "device_id": "{id}" }
Zapier Trigger multi-app automation { "trigger": "new_event", "value": "{data}" }

Troubleshooting

  • Error 400/401?
    Check the endpoint URL, headers, or missing required fields.

  • Nothing happens?
    Confirm the trigger is firing and the webhook node is connected properly.

  • Unexpected format?
    Ensure you're using the correct payload type (e.g., JSON vs form data).

  • Slow response?
    Consider pushing data asynchronously or logging results for follow-up processing.


Next Steps

👉 How to Set Up Real-Time Notifications
👉 Using AI Agents to Create Webhook Payloads
👉 Logging External Events in Tables
👉 Using Webhooks with Zapier or Make