Dry-runs the supplied trigger bindings + sample payload through the same resolver the dispatcher uses at fire time
Returns one entry per submitted binding. On success the entry carries the resolved `parameters` dict the agent executor would receive; on failure the entry carries an `error` message (unknown parameter name, type-coercion mismatch, agent with no deployed revision).
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The tenant identifier
Bindings to preview. One Fruxon.Model.Triggers.PreviewBindingResult comes back per binding in the same order.
Sample payload the resolver walks. Should mirror the canonical per-source shape on Fruxon.Model.Triggers.TriggerFirePayload so the preview matches what the real dispatcher would build.
Optional content filter to dry-run against Fruxon.Model.Triggers.PreviewTriggerRequest.Payload. When supplied, the response's Fruxon.Model.Triggers.PreviewTriggerResponse.FilterMatched reports whether this payload would pass the filter (and therefore reach the bound agents) at fire time. Null = no filter = always matches.
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/triggers/preview" \ -H "Content-Type: application/json" \ -d '{ "payload": { "source": "UNSPECIFIED" } }'{
"bindings": [
{
"agentId": "string",
"parameters": {},
"error": "string"
}
],
"filterMatched": false
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Partial update
Applies a partial update: only the non-null fields of the request are written. `Kind` is immutable. Agent bindings are managed through the nested `bindings` sub-resource, not this endpoint.
Renders a draft work shape's stage prose the way the runtime will.
Returns one entry per submitted stage: a PROCESS stage's instruction with every declared `{{name}}` expanded and the whole `user_query` its agent receives (the instruction plus the item payload the dispatcher appends), an ASK stage's fully composed question (framing, the numbered item list labelled through `labelPath`, and the reply trailer), and any reference that expands to nothing. Rendered with the automation's own items when `triggerId` names one that has any, and with stand-ins otherwise. Read-only: it composes strings. Nothing is saved, no batch is opened and no run is dispatched. The draft is deliberately not validated, because a shape mid-edit usually is not valid and that is exactly when the preview is worth having. See `docs/design/item-ledger.md §8.2`.