Lists the automation's work items.
The Work view's item grid. Filter by stage and status; the UI defaults to DEAD + FAILED first, because the dead-letter queue is the reason this view exists. `ignoreReason` narrows to the items one exclusion reason set aside, matched whole and case-sensitively, and is the filter that makes `totalCount` the number `items:redrive` will confirm for the same selection. Without it the client could see "1,204 IGNORED" and the 29 rows its current page happens to hold, and nothing in between.
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
The maximum number of items to return per page
int32int32Opaque pagination token returned by an external service. Pass it back unchanged rather than interpreting it as an offset.
Sort order.
Optional stage filter.
Optional status filter.
"UNSPECIFIED" | "READY" | "CLAIMED" | "WAITING" | "DONE" | "FAILED" | "DEAD" | "IGNORED"Optional exclusion-reason filter; selects IGNORED items only.
Optional cohort filter — the members of one cohort.
uuidOptional free-text search: a case-insensitive substring of the item's key, its label, or any string or number in its data — the source record and what its stages produced, so an item can be found by a customer name or a policy number its subject line never carried.
Optional, repeatable: items whose data holds a value at a path — destination=SKIP — or does not —
destination!=SKIP, which also keeps items without the path. The path is a data key, dotted for a
nested one; the value is matched whole and case-sensitively, as a string and as the number, boolean or
null it spells. Clauses combine with AND; at most ten.
Optional: only WAITING items waiting on PERSON (an ASK stage's question) or TIME (a WAIT
stage's due time). Sort by wakeAt to see what wakes next.
"UNSPECIFIED" | "PERSON" | "TIME"Optional: only items started by hand — API through items:admit, AGENT by a conversation
agent's start_work_item. Items a listing or an event admitted carry neither.
"UNSPECIFIED" | "API" | "AGENT"Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/triggers/497f6eca-6276-4993-bfeb-53cbbbba6f08/ledger/items"{
"items": [
{
"id": "00000000-0000-0000-0000-000000000000",
"ledgerId": "00000000-0000-0000-0000-000000000000",
"itemKey": "string",
"label": "string",
"stageId": "string",
"status": "READY",
"stageAttempts": 0,
"nextAttemptAt": 0,
"lastError": "string",
"admittedAt": 0,
"terminalAt": 0,
"lastExecutionRecordId": "00000000-0000-0000-0000-000000000000",
"batchRunId": "00000000-0000-0000-0000-000000000000",
"batchId": "00000000-0000-0000-0000-000000000000",
"lastBatchId": "00000000-0000-0000-0000-000000000000",
"data": null,
"admittedVia": "API",
"admittedBy": "string",
"admittedByExecutionRecordId": "00000000-0000-0000-0000-000000000000",
"wakeAt": 0,
"waitingFor": "PERSON",
"cost": 0,
"runs": 0
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Shows what is gathering at the automation's batch stages.
Items at a stage that processes in batches wait, unclaimed, until their group closes: when it is full, when its oldest item has waited the stage's window, or when nothing upstream can still feed it. For each batch stage this returns its rules, its runs in flight, and each group with its size, where it stands and — while it is still gathering — when its window closes it. A fire with `closeGathering` closes them all now.
Starts one work item by hand.
For an automation whose work shape declares an `onDemand` block: admits one item at its first stage, from `data` checked against the block's declared inputs. The item key is `itemKey`, or composed from `data` at the block's `keyPaths`; when both are given they must agree. A credential-named key anywhere in `data` is refused — store the value in Secrets. <b>Idempotent on the key.</b> 201 with `created: true` for a new item; 200 with `created: false` and the item that already holds the key, unchanged, whatever its status and whatever this call's data says — never a 409. Corrections go through `:setData`; a finished item is not restarted. A repeatable operation needs its occurrence (an invoice number, a cycle) among the key paths. A paused automation still admits; `paused: true` says nothing will work the item until it is resumed. `stageId` is refused: an item starts at the first stage. Needs `triggers:fire`.