Custom Integrations | Integration Layer

HTTP + REST API nodes, both directions

Ingest via POST to a Rayven-hosted endpoint, or pull from external systems via GET/POST/PATCH. Supports JSON and XML. Bearer token authentication built-in.

SQL read + write against live databases

Execute queries against MySQL or MSSQL using a configured connection string. Supports reads, writes, custom queries + auto-insertion of payload data into fields.

File ingestion via FTP, FTPS, SFTP + S3

Pull files from FTP/FTPS/SFTP folders or AWS S3 buckets on a configurable schedule. Handles JSON, CSV, XML + compressed formats with configurable encoding.

Outbound webhooks + write nodes

Push workflow data to any external system via HTTP POST, write to FTP destinations, or trigger downstream APIs. Supports JSON, XML, and String output formats.

AWS Kinesis streaming ingestion

Ingest high-volume event streams from AWS Kinesis with configurable polling intervals and UID mapping from a nominated JSON key.

AMQP message queue connectivity

Consume messages from AMQP-compliant brokers. Useful for event-driven architectures where data arrives asynchronously from queue-based systems.

Pre-built connectors are configured for specific software products - HubSpot, Xero, SAP + others. The Dynamic Integration Node is for systems without a standard API - industrial devices, legacy databases, machinery + proprietary hardware. It connects by configuration in the workflow builder, without coding.

When a system cannot be reached by a pre-built connector, standard protocol node, or the Dynamic Integration Node. Typically: genuinely proprietary protocols, unusual file structures, or legacy assets with no data output. Rayven's team builds and deploys the script - you don't need to write it yourself.

Yes. Outbound nodes sit at the end of any workflow - Output to HTTP, API write, FTP output, SQL write, Output to Modbus + MQTT. Ingest, process, act, write back - all within one platform.

All standard formats - JSON, XML, CSV, String, compressed files - plus binary and proprietary structures via custom scripts. Data is normalised on ingestion so downstream workflow nodes always work with a consistent schema.

In practice, no. The combination of pre-built connectors, standard protocol nodes, the Dynamic Integration Node, and custom scripting covers every integration scenario we have encountered. If your system has data, there is a path in.

The Dynamic Integration Node connects by configuration - no code written. It covers devices, databases + machinery that have a known interface but no standard API. Custom scripts go a step further, enabling connection to systems with no usable interface at all.

Yes. A single workflow can ingest from an MSSQL database, a Modbus-connected PLC, an HTTP API, and a file drop simultaneously. All data is normalised per UID and flows through the same pipeline. IT/OT convergence is a native capability, not an add-on.

Scripts are maintained by Rayven's team as part of your ongoing service arrangement. If a source system changes its structure or output, we update the script. This is included in your support agreement - you are not responsible for maintaining integration code.

For standard protocol + Dynamic Integration Node connections, typically within hours to days of configuration. For custom scripts, most are live within one to two weeks. Our platform-first approach means we are not starting from scratch.

Both. The workflow builder's low-code nodes are configurable by any technically proficient user. For custom scripts, Rayven's team handles development + deployment. As your team's confidence grows, we can hand over ownership of any integration at any point.

By Industry

By Job Role

Enterprise

Library

Our Company

Platform Home > Integration Layer > Custom Integrations

Custom integrations.

Build integrations to anything.