Intro to Workflows
      Back to home
      1. Home
      2. 5: Automation & Workflows
      3. Intro to Workflows

      Rayven Connectors Overview

      Rayven offers a suite of built-in connectors that enable seamless integration with popular third-party platforms and services. These connectors allow you to ingest, synchronize, and act on data from external systems

      workflow

      Rayven offers a powerful set of prebuilt connectors that make it easy to integrate with third-party platforms, tools, and services—without needing to write code. These connectors allow your workflows to ingest, synchronize, and act on external data, enabling seamless end-to-end automation.

      💡 Can’t find a connector you need? Use the API Node to integrate with any RESTful service—or contact us to request a new connector.

      Connector Categories

      Rayven connectors span multiple industries and data domains, supporting a wide range of integration scenarios. Key categories include:

      • Operational Systems: SCADA, PLCs, sensors, and telemetry inputs

      • CRM & Customer Platforms: Lead management and customer engagement tools

      • ERP & Accounting: Billing, invoicing, and procurement systems

      • Communications: SMS, email, voice, and messaging apps

      • Cloud Services: File sharing, spreadsheets, content apps

      • AI & Analytics: LLMs, ML APIs, data enrichment sources

      • E-commerce: Payment systems, digital receipts

      • Asset & Field Services: QR codes, barcoding, field data collection

      Each connector includes one or more workflow nodes (Input, Output, Trigger), supports authentication, and is designed to fit the API structure of the target system.

      Example Connectors

      Connector Purpose
      OpenWeather Fetch real-time or forecast weather by location; use for environmental and logistics workflows
      HubSpot Sync lead/contact data; trigger marketing or CRM actions
      Google Sheets Read/write to shared spreadsheets for planning or reporting
      OpenAI Generate summaries, content, or classifications using GPT
      Twilio Send/receive SMS, WhatsApp, or voice alerts
      Xero Sync invoices, payments, contacts in accounting workflows
      QuickBooks Automate transaction sync, inventory tracking, and alerts
      QR Tiger Generate QR codes for asset tracking and process identification
      Slack Send internal messages or trigger workflows from commands
      Stripe Manage subscriptions, payments, and refund logic
       

      Setting Up a Connector Node

      When adding a connector node to a workflow, you’ll typically configure:

      Field Description
      Node Name* Descriptive label for the connector node
      API URL* Full URL for the resource endpoint
      Endpoint/Resource (If applicable) API route (e.g., /v1/Sims)
      Auth Fields Account SID, API token, OAuth credentials
      Trigger Type (Optional) Event-based or scheduled polling
      Polling Frequency Interval between checks (e.g., every 15 mins)
       

      These fields vary based on the connector’s protocol and security requirements.

      Using Connectors in Workflows

      Most connectors include:

      • Input Node: To ingest data or listen for triggers

      • Output Node: To push updates or create records

      • Authentication Options: API Key, OAuth, or environment variables

      You can use Expression Nodes to transform or format data before sending, and to parse or re-map responses from external systems.

      Can’t Find a Connector? Use the API Node

      If the system you want to integrate doesn’t have a built-in connector:

      Use the API Node to connect any REST API:

      • Set the HTTP Method: GET, POST, PUT, DELETE

      • Configure headers, body, and query parameters

      • Use workflow variables to dynamically build requests

      • Parse JSON responses into downstream nodes

      This node is ideal for custom services, niche tools, or proprietary platforms.

      Example: Use the API Node to connect to an internal ERP, retrieve open orders, and push the results to a dashboard.

      Best Practices

      • Secure credentials using encrypted environment variables

      • Use retry logic for API-sensitive connectors

      • Test connectors in sandbox environments before going live

      • Document token expiration rules and re-authentication steps

      • Monitor connector logs and analytics to track performance and reliability

      Q&A

      Q: How do I authenticate connector nodes?
      A: Most connectors support OAuth, API Key, or Basic Auth. Fields are entered securely in the node configuration.

      Q: Can I customize payloads sent to or received from connectors?
      A: Yes. Use Expression Nodes to format requests or parse responses before passing them to other nodes.

      Q: What if I need to connect to a platform that’s not listed?
      A: You can use the API Node to build a custom integration. If the platform supports REST APIs, Rayven can connect to it.

      Q: Can I use multiple connectors in a single workflow?
      A: Absolutely. Rayven workflows are modular, allowing you to chain inputs and outputs from multiple systems together.

      Q: What’s the difference between a connector and an API node?
      A: A connector is a pre-configured node for a specific service. The API Node is generic and used for building custom REST integrations.

      Q: Can connectors be event-driven?
      A: Yes. Some connectors support real-time event triggers, while others use scheduled polling to check for updates.

      Rayven connectors drastically reduce integration complexity, enabling fast, scalable automation between your systems. For help configuring a connector or to request a new one, contact Rayven support.