Webhook-install metadata for a messaging connector.
Catalog metadata, not per-tenant data. Returns the provider display name, whether Fruxon can register the webhook programmatically (`supportsAutoInstall`, derived from the live installer registry), and the HTML connect / webhook instructions. Drives the activation UI's install panel so the frontend renders from the backend rather than a hardcoded provider map. 404 when the integration is not a messaging connector.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/connectorInfo"{
"provider": "string",
"displayName": "string",
"supportsAutoInstall": false,
"providerInstructionsHtml": "string",
"webhookInstructionsHtml": "string"
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists channel types this integration provides.
Catalog metadata, not per-tenant data. Slack provides `channel`/`im`/`group`; Telegram provides `chat`; integrations that don't deliver messages return an empty list. Drives the participant address picker's input hints and the future integration tab's Channels section.
Consumes temporarily stored OAuth credentials from a completed application-level OAuth flow and creates an `IntegrationAuth` record bound to the specified integration config.
The credential key is returned to the frontend via the OAuth success redirect after the user completes authorization. The resulting connection is shared by every agent that references the target config. The credential key is single-use.