FruxonDocs
IntegrationsCore

Lists every integration that declares at least one trigger descriptor.

Drives the new-trigger picker so the operator doesn't see the 40+ trigger-less integrations in a long flat dropdown. Each row is `{ integrationId, displayName, triggers[] }`; consumers can pick an integration and use the embedded `triggers` array directly without a second round-trip.

GET
/v1/tenants/{tenant}/integrations/triggerTypes

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

tenant*string

The tenant identifier

Response Body

curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/triggerTypes"
[
  {
    "integrationId": "string",
    "displayName": "string",
    "triggers": [
      {
        "id": "string",
        "displayName": "string",
        "description": "string",
        "kind": "UNSPECIFIED",
        "requiresConfig": false,
        "payloadFields": []
      }
    ]
  }
]
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Lists trigger types this integration emits.

Catalog metadata, not per-tenant data. Examples: GitHub emits `github.pull_request.opened`; the System integration emits `schedule.cron`. The runtime `Trigger` entity binds one of these types to one or more agents.

Verifies that the provided auth configuration can successfully connect to the integration.

Only supported for auth methods with `ConfigTestSupported = true`. Returns 400 if the auth method does not support verification.