Actions50
- Company Actions
- MS Manual Actions
- Company Information Actions
- Organisation Chart Actions
- Products & Services Actions
- Design & Development Actions
- Scope of Certification Actions
- Key Processes Actions
- Interested Parties Actions
- USPs Actions
- Finalise Policy Actions
- Normative References Actions
- List of Assets Actions
- Risk Assessment Actions
- Objectives Actions
- Customer Feedback Criteria Actions
- Supplier Evaluation Actions
- Supplier Evaluation Criteria Actions
- Terms and Definitions Actions
- Hazard Identification Actions
- Elimination of Hazards Actions
- Multi-employer workplace Actions
- Workers Representative Actions
- Annex A Controls Actions
- Communication Actions
- Finalise Manual Actions
- Finalise SOA Actions
- Status Actions
- Task Actions
- User Actions
- Workflow Actions
- Workflow Entry Actions
Workflow Entry → Update Workflow Entry
AI-generatedSummary
Updates an existing MSFrog workflow entry by UUID, setting its name and description and optionally sending step assignments and metadata. Uses the configured MSFrog credentials and an optional node-specific Base URL override.
Inputs
- Base URL Override — Optional URL that overrides the Base URL in credentials for this node.
- Workflow Entry UUID (required) — UUID of the workflow entry to update.
- Entry Name (required) — Name to set on the entry.
- Description — Description to send with the update; defaults to an empty string.
- Step Assignments — JSON array of step assignment objects using backend field names. Sent only when the array contains at least one item.
- Meta (JSON) — JSON metadata to store with the entry, such as email_ids or thread_ids. If provided and non-empty, email_ids and thread_ids may be augmented from the input item's meta, workflowEntryMeta, or emailMeta fields.
Output shape
A single output item per input item containing the API response as JSON.
Sends a PUT request to /api/userworkflows/{workflowEntryUuid}. The request includes name and description, and includes step_assignments and meta only when non-empty. Invalid JSON inputs or API errors fail the operation unless Continue On Fail is enabled, in which case the corresponding output item contains an error field.