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.
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
Optional sample payload, and optional per-pass bounds.
Optional synthesized inbound payload to nest under
TriggerFirePayload.Body["payload"]. The mapping resolver
walks dotted paths into this dict (e.g.
{{payload.text}}, {{payload.message_attributes.repository}})
so operators can validate their Mappings tab wiring without
provider-side webhook subscription.
Only valid for TriggerKind.IntegrationEvent. Schedule fires reject a non-null value with 400 — their trigger context is fully synthesized from the row's columns.
Stop admission after this many genuinely-new items on this pass. Zero leaves the source untouched, so the pass moves only what is already in the ledger.
Work-shape automations only; a fire that has no ledger to bound rejects it with 400. Omitted means the unbounded admission a scheduled pass runs.
int32Stop claiming after this many items across every stage of this pass. Zero admits without dispatching anything.
Work-shape automations only. Omitted leaves the automation's own per-stage claim limits as the only ceiling, which is what every pass did before.
int32Claim only at these stages, by their declared ids. A stage the work shape does not declare is rejected with 400 rather than quietly claiming nothing.
Work-shape automations only. Omitted or empty claims at every stage, in declared order. Naming a stage also lifts its hold, if its runs were being refused (an agent over budget, a workspace out of credits) and the ledger had stopped claiming there.
Close every gathering group at the batch stages this pass reaches, instead of waiting for each to fill or for its oldest item to wait out the window. Each group still runs one batch at a time if its stage says so, and the stage's running cap still applies. Work-shape automations only; harmless when no stage processes in batches.
Open a cohort with this pass — optionally sampled — or add the pass to the open one. See ItemLedgers.LedgerCohortRequest.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08:fire" \ -H "Content-Type: application/json" \ -d '{}'null{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}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.
Returns a single trigger with its current agent bindings.
Fetches one trigger by id, including the set of agents it currently fires. Returns 404 when no trigger with that id exists in the tenant.