Crate forge_connectors 

forge-connectors - one module per external integration, inbound or outbound.

Each connector module owns the network client, payload mapping and matching rules for one external integration. The GotifyHost port, implemented by forge-workspace, is the only workspace state, delivery or TLS-trust plumbing a connector may reach, so a connector stays stream + mapping and is testable offline. Three connectors exist today - Gotify pushes through a host port, Slack is called by the workspace directly, and Vaultwarden is an in-process HTTP client the vault family fronts - so there is still deliberately no generic connector trait.

Modules

gotify

The Gotify connector: WebSocket receive stream, /application + /message REST lookups, the subscription matcher, and the reconnecting subsystem pump that routes matched messages into the host’s sessions.

slack

The Slack Web API client: one uniform POST per method, form params, Bearer token, and the envelope rules that turn a logical failure into an error.

vault

The Vaultwarden connector: the Bitwarden client API this family talks to.