Fire action by ID

Fires a workflow action, specified by identifier, on a target contentlet.

Returns a map of the resultant contentlet, with an additional AUTO_ASSIGN_WORKFLOW property, which can be referenced by delegate services that handle automatically assigning workflow schemes to content with none.

Use this endpoint to fire actions that are not represented as SystemAction tokens (NEW, EDIT, PUBLISH, etc.). The two most common are Move and Copy on the System Workflow scheme.

Move action — relocates a contentlet to a new folder/host. Request body shape (note: pathToMove is a sibling of contentlet, not nested inside it):

{
  "contentlet": { "identifier": "<contentlet-identifier>" },
  "pathToMove": "//<siteHost>/<folderPath>"
}

Alternative shapes (contentlet.host+contentlet.folder, contentlet.hostFolder, path instead of pathToMove) all return 400 "The host path is not valid: null".

Copy action — clones a contentlet. Fire with ?identifier=<source-id> and an empty body (or {"contentlet": {"identifier": "<source-id>"}}). The Copy action id on the default System Workflow scheme is 963f6a04-5320-42e7-ab74-6d876d199946; retrieve it for other environments via GET /api/v1/workflow/schemes/{schemeId}/actions. ⚠️ The response entity returns the source contentlet, not the newly-created copy — locate the copy via a follow-up POST /api/content/_search ordered by modDate DESC. The copy lands in SYSTEM_HOST / SYSTEM_FOLDER; destination hints (pathToMove, host, folder, hostFolder) are silently ignored. Fire the Move action afterwards to relocate.

When chaining workflow actions or reading state back immediately after firing, pass indexPolicy=WAIT_FOR on each call. The default DEFER is asynchronous and can return stale index reads for several seconds, which can mimic server-side state bugs. For isolated one-off fires where nothing reads the result, leave the default.