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.
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/triggers"[
{
"id": "string",
"displayName": "string",
"description": "string",
"kind": "SCHEDULE",
"requiresConfig": false,
"payloadFields": [
{
"path": "string",
"type": "UNSPECIFIED",
"description": "string",
"group": "UNSPECIFIED",
"examples": {
"default": {
"value": "string"
}
}
}
]
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Updates an existing integration.
Omit credential fields to keep existing values unchanged.
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.