How-to

Add a connector

Connectors are named, tenant-scoped endpoints. Many integrations can share one. Credentials live as secret references, not as copies on every graph.

In the console

Open Connect → new connector.
Choose a family (HTTP, file, queue, database, an industry protocol).
Fill required settings. For TLS, pin a CA bundle for private authorities instead of turning verification off.
Save. Then Probe.
- Dry-run confirms the connector can be built.
- Live sends a real request, write, or publish using a sample you provide (or a benign synthetic one).
In Build, bind a source or destination node to that connector (source_ref / destination_ref), or paste settings inline on the node.

Paths on disk

File connectors, archives, and certificate files resolve through the shared data directory. Paste the host path you see in Finder or Explorer when the installer mounted that folder. A path outside the share fails fast with misconfigured rather than silently doing nothing.

From the API

curl -s "$SIRIUS/connectors"                    # catalog
curl -s "$SIRIUS/connectors/http"               # one family + settings schema
curl -s -X POST "$SIRIUS/connectors/http/validate" \
  -H 'content-type: application/json' \
  -d '{"settings":{"url":"https://example.org/ingest"}}'

curl -s -X POST "$SIRIUS/destinations" -H 'content-type: application/json' -d '{
  "tenant_id":"default",
  "name":"Warehouse API",
  "kind":"http",
  "settings":{"url":"https://warehouse.example.org/ingest"}
}'
curl -s -X POST "$SIRIUS/destinations/warehouse-api/probe" \
  -d '{"mode":"dry_run"}'

Live probes require runtime:connector:probe at the caller’s own scope.

In a transform

Once a connector is wired, call it from the script:

const rows = sirius.db.query("warehouse", "select name from sites where id = ?", [id]);
const res = sirius.http.post({ url: dest, body: sirius.json.encode(out) });

Those calls stay simulated in Studio until Live I/O is on.

More families: Connectors.