BARRYBARRY
Documentation

Connector catalogue

Every source, sink, trigger and alert channel.

This is the index of every connector BARRY ships, grouped by family. Each connector has its own page with its capabilities, what it does, and its key configuration. The capabilities a connector derives are one or more of Source · Sink · Trigger · Alert (see Connections). Capability chips appear on every connection row and in the New connection picker; the kind itself is fixed once a connection is created.

Credentials for every connector are encrypted at rest and never returned to the browser — leave a secret blank when editing to keep the stored value, or use an @kv(...) vault reference.

Relational databases

Read with a parameterised SQL query and streamed as Apache Arrow; relational sinks land data through bulk loads.

Enterprise applications

  • SAP OData — Source — read SAP exposed OData services.
  • SAP RFC — Source — read SAP tables / function modules over RFC.

Object stores

Sinks that hold where data goes; the format comes from the paired Output Format.

File transfer

Warehouses & lakehouses

Self-contained sinks that own both staging and apply, so they need no separate output format.

Streaming

Message brokers — publish run output as a Sink, or start a transport as a Trigger (see Triggers).

HTTP APIs

Source connectors that read JSON over HTTP.

Inbound messaging (Trigger only)

Alert channels (Alert only)

Outbound notification targets referenced by an Alert.