Roll-up of delivery outcomes over a time window.
Powers the right-rail delivery-summary card — the one that replaces the bare "Last fired" line with a received / fired / filtered breakdown so operators can tell at a glance whether the filter is the reason their agent isn't running. Default window is 24 hours; the max is 30 days.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The trigger identifier.
uuidThe tenant identifier
Query Parameters
Window length in hours (default 24, max 720).
int32Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/events:summary"{
"windowHours": 0,
"received": 0,
"fired": 0,
"filtered": 0,
"filterError": 0,
"lastDeliveryAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists delivery attempts on the trigger, newest first.
Backs the Events tab on the trigger detail page. Each row records what the dispatcher did with one inbound that structurally matched the trigger — fired, dropped by the content filter, or fired fail-open because the filter threw. Without these rows, the filter-rejected case presents in the UI as identical silence to "the webhook never reached us"; with them, the operator can tell whether to fix the webhook or the filter rule. Cursor pagination via before (a `createdAt` timestamp from the last row of the previous page).
Fires the trigger immediately against every bound agent's current revision.
Fires bound agents using their current revisions. This is a real execution: tools may send messages or modify external systems. Returns 404 for an unknown trigger. samplePayload simulates an inbound payload for INTEGRATION_EVENT triggers; SCHEDULE triggers reject it with 400. A scheduled agent still running its previous execution returns 409; resolve or cancel it before firing again. Work-shape automations run a sweep instead: maxAdmit bounds new admissions (zero admits none), maxDispatch bounds item claims, stageIds restricts stages and closeGathering closes collecting batches. These bounds apply only to this invocation and do not alter the schedule. Unknown stages return 400.