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).
Test-fires the trigger immediately against every bound agent's current revision.
Fires the trigger on demand, bypassing its schedule or inbound event. Every bound agent is run against its current revision, exactly as a real firing would. Use it to verify a trigger's wiring without waiting for the next scheduled window. Returns 404 when the trigger does not exist. Phase 10f — when the request body carries a `samplePayload`, the dictionary nests under `Body["payload"]` exactly like an inbound message from `IntegrationConfigMessageReceiver`. Lets operators validate the full mapping → agent-enqueue pipeline before any provider-side webhook wiring is in place. Only valid for IntegrationEvent triggers; Schedule fires reject the field with 400.