Workflow Run → Update
AI-generatedSummary
Update an existing Process Street workflow run’s metadata, form values, and checklist selections. Fetch the current run first to preserve unspecified metadata, then apply metadata and individual form field updates.
Inputs
- workflowId (required) — Required workflow template name or ID. Loads available form fields and checklist choices and identifies File/MultiFile fields for uploads; the run itself is targeted by workflowRunId.
- workflowRunId (required) — Required ID of the run to update, typically supplied by an expression from a previous node. Despite the display label, a run name is not resolved.
- updateFields — Optional name, status (Active, Archived, or Completed), due date, and shared flag. Unspecified values retain current metadata. Empty name or due date also retains the current value; a supplied due date must be valid and more than 24 hours ahead.
- formFields — Optional values mapped to the selected workflow’s supported form fields. Null, undefined, and empty strings are skipped; false and zero are sent. File/MultiFile values must be downloadable URLs: the node downloads and uploads their contents.
- multiSelectValues — Optional checklist choices grouped by field. Include every choice you want checked for each field being updated, since its selections are replaced. Fields with no selected choices are left unchanged, so an empty selection cannot clear a checklist.
Output shape
One workflow run JSON record per input item.
Returns the fetched run merged with the supplied updateFields, rather than a refreshed API response; updated form values are not fetched back. Empty metadata values may therefore appear in output even when the existing value was sent to the API. Form field failures can occur after metadata and other fields have been updated: normally they raise an error; with Continue On Fail, the record includes formFieldError. Other failures return an error-only record with Continue On Fail.