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.
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 for IntegrationEvent triggers.
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 Fruxon.Model.Triggers.TriggerKind.IntegrationEvent. Schedule fires reject a non-null value with 400 — their trigger context is fully synthesized from the row's columns.
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
}