Skip to main content

Sinks

Sinks define where your processed data goes. They are the outbound connection endpoints that write messages to files, cloud storage, message queues, and other external systems.

Overview​

In layline.io, a Sink is an asset that configures how and where output messages are delivered. Sinks work together with Output Processors — the processor determines what to send (which messages, in what format), while the Sink determines where to send it (which destination, using what connection parameters).

Sinks handle connection details, authentication, retry logic, and destination-specific behaviors. Once configured, a single Sink can be reused across multiple workflows and output processors.

Available Sinks​

File System​

Sinks for writing to traditional file systems and network shares.

SinkDescription
Sink File SystemWrite files to the local file system accessible by the Reactive Engine. No Connection asset required.
Sink NFSWrite files to Network File System (NFS) shares. Requires an NFS Connection.
Sink SMBWrite files to SMB/CIFS shares (Windows file shares). Requires an SMB Connection.
Sink FTPWrite files to FTP or FTPS servers. Requires an FTP Connection.
Sink WebDAVWrite files to WebDAV-enabled servers. Requires a WebDAV Connection.

Cloud Storage​

Sinks for major cloud object storage providers.

SinkDescription
Sink S3Write objects to Amazon S3 or S3-compatible storage (GCS, IONOS, etc.). Requires an AWS Connection.
Sink GCSWrite objects to Google Cloud Storage buckets. Requires a Google Cloud Connection.

Messaging & Streaming​

Sinks for event streaming, message queues, and event buses.

SinkDescription
Sink KafkaPublish messages to Apache Kafka topics. Requires a Kafka Connection.
Sink KinesisWrite records to Amazon Kinesis Data Streams. Requires an AWS Connection.
Sink SQSSend messages to Amazon Simple Queue Service queues. Requires an AWS Connection.
Sink SNSPublish notifications to Amazon Simple Notification Service topics. Requires an AWS Connection.
Sink EventBridgeSend events to Amazon EventBridge event bus. Requires an AWS Connection.

Microsoft 365​

Sinks for Microsoft cloud services.

SinkDescription
Sink OneDriveWrite files to Microsoft OneDrive. Requires an MSGraph Connection.
Sink SharePointWrite files to Microsoft SharePoint document libraries. Requires an MSGraph Connection.

Network & Protocol​

Sinks for direct network protocols and abstraction layers.

SinkDescription
Sink WebSocketSend data to a WebSocket server as a client. Connection parameters configured inline — no Connection asset required.
Sink Virtual File SystemWrite to any backend supported by a Virtual File System Connection (local, SMB, NFS, etc.) through a unified abstraction. Requires a Virtual File System Connection.

How to Choose a Sink​

If you need to...Use this Sink type
Write to local diskFile System
Write to network sharesNFS, SMB, FTP, or WebDAV
Store objects in cloudS3 or GCS
Stream eventsKafka or Kinesis
Send to message queuesSQS
Push notificationsSNS or EventBridge
Write to Microsoft cloudOneDrive or SharePoint
Real-time bidirectionalWebSocket
Flexible backend switchingVirtual File System

See Also​

  • Sources — Inbound connection endpoints that read data from external systems (the counterpart to Sinks)
  • Output Processors — Workflow processors that determine what data to send to a Sink
  • Connections — Reusable connection configurations (authentication, endpoints) used by many Sinks
  • Formats — Define how data is structured when written by Sinks

Sink Reference Documents​

Last updated on