Connector model

Each connector should be understood in four parts:

Part	Responsibility
Configuration	Provider identity, connection state, and project binding.
Credentials	Secret material held by the platform and scoped to allowed targets.
Actions	Outbound provider operations invoked through an admitted capability.
Events	Inbound webhooks or provider events reconciled into project runtime state.

Connector pages should document prerequisites, supported actions, directionality, webhook verification, rotation, and failure behavior. The generated connector reference is the canonical public inventory produced from Core connector metadata.

Start here

Build

Application composition

Backend

Integrations

AI clients

API reference

Platform