Create Integration
Create a manual integration, fully configured.
Which of credentials_ref, provider_account_info, mcp_config and
webhook_config a provider needs is described by its setup_fields in the
integration catalog. Secret-bearing fields take a plaintext value — stored
as a workspace secret — or an existing {{secrets.NAME}} reference.
Leave allowed_tools unset to expose every tool the server lists. OAuth
providers are connected from the dashboard instead.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
1 - 120custom_mcp, google_calendar, cal_com, calendly, asana, jira, hubspot, exa, tavily, resend, rocketreach, telegram 11 - 2001 - 16384^$|^[a-z][a-z0-9_]{0,23}$Response
Successful Response
Public API representation of an integration (HTTP + CoPilot).
oauth, manual Complete capabilities projection — always the same shape for every provider.
Derived from ProviderSpec at response time; never stored in the DB.
custom_mcp, google_calendar, cal_com, calendly, asana, jira, hubspot, exa, tavily, resend, rocketreach, telegram active, disabled, needs_reconnect, error Where the provider delivers, and whether anything has arrived yet.
Status rather than instructions: a chat provider registers its own webhook when a trigger is enabled, so nobody has to paste this URL anywhere. It is here for support — "has anything ever arrived on this connection".