Connector Library

Choose where alerts and actions go.

The Connector Zoo describes where trigger actions go next. It separates connector availability from connector configuration so the runtime can expose integrations without forcing every workspace to enable all of them.

Model Library Trigger Library Connector Library

Current Scope

Connect everything

The runtime docs describe Telegram, Apple Messages, webhooks, and optional plugins like Govee Light Connection as examples of Connector Zoo coverage.

Built-in

Telegram

Send trigger notifications to Telegram subscriptions configured in the workspace.

Built-in

Apple Messages

Deliver trigger notifications through the Apple Messages integration path.

Outbound

Webhooks and APIs

Use structured downstream delivery paths instead of coupling actions to the runtime.

Optional

Govee Light Connection

Expose device-control actions through an optional connector plugin rather than the core default set.

Connector semantics

Availability and configuration are not the same thing.

A connector entry can exist in the zoo without being fully configured in the workspace. That separation keeps the catalog understandable while preserving local control.

Plugin-backed

Optional integrations stay optional

The Govee plugin is a good example: it adds a connector entry without forcing every installation to treat light control as a core capability.

Example Connector

Govee shows how the library can grow without bloating the default runtime.

The current Govee v1 scope is limited and concrete: validate the API key, discover devices, read optional state, and send light-control actions such as power, brightness, color, temperature, and scenes.

What stays small by default

Core connector coverage is intentionally narrow
Optional plugin connectors can be surfaced after restart
Catalog presence does not imply the connector is configured yet

What a connector ultimately does

The Connector Zoo controls where events are sent after the runtime decides an alert or action should fire.

Connector Zoo in the runtime

Review the current repository wording for connector catalog behavior and optional plugins.

Read the README

Contribute integrations

Connector contributions can target plugin bundles, security hardening, or the connector-catalog flows that expose installable integrations cleanly.

Open the runtime repository