Connector Documentation

Connectors translate product APIs and events into the same native AIP capability, identity, lifecycle, policy, and error model.

Current Connector Evidence

Connector	Implemented boundary	Retained qualification
Cal.diy	81 typed scheduling, booking, calendar, conferencing, and webhook capabilities	Exact-upstream isolated-live report retained
Hermes Agent	API server, sessions, runs, streams, cancellation, channel and governed operator/delegation behavior	Two-instance isolated-live report retained
CrewAI	Authenticated sidecar, blocking and streaming execution, cancellation, idempotency, and recovery fencing	Exact-upstream narrow qualification exists; complete isolated-live campaign is not retained
Dify	App and workflow calls, streaming, cancellation, and human-input mapping	Complete isolated-live campaign is not retained
Chatwoot	Signed webhook ingress, channel egress, status, handoff, and loop prevention	Complete isolated-live campaign is not retained
Support and enterprise sandboxes	Deterministic systems of record used by protocol E2E tests	Test-only; not product connectors

Connector implementation and external qualification are separate claims. Read Implementation Status before citing a connector as qualified for a release or deployment.

Documents

• Cal.diy Connector
• Hermes Agent Connector
• Chatwoot Connector
• Dify Connector
• CrewAI Connector
• Pinned Upstream Baselines
• Live Product E2E
• Testing and Evidence Index

To implement a new product boundary, start with Build a Connector. To migrate an existing connector, use Upgrade a Connector to the Frozen SDK.