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
MS Manual → Hazard Identification Actions
AI-generatedSummary
Call an MSFrog MS Manual hazard identification endpoint for an ISO engagement. Choose an action to retrieve or set hazard identification, mark it complete or incomplete, or manage assignments and their actions.
Inputs
- Base URL Override — Optional URL that overrides the base URL in the MSFrog credentials for this node.
- ISO Engagement ID (required) — Engagement ID used to build the MS Manual API path.
- Action (required) — Select an action: get or set hazard identification; complete or mark it incomplete; delete all assignments or a specific assignment; set an assignment; or set or delete an assignment action.
- Route Params (JSON) — Values for route placeholders. Supply assignUuid for actions targeting an assignment, and actionUuid when targeting an assignment action. Placeholder values are required for the selected route and URL-encoded.
- Body (JSON) — JSON request payload used by the set hazard identification, set assignment, and set assignment action routes. Ignored for routes that do not accept a body.
Output shape
One n8n item per input item, with the API result and request metadata in its JSON.
The output includes operation, selected route value, engagement ID, HTTP method and path, route parameters, and body; the API result is merged into these fields and also exposed as response. If the result contains error, details, or err_code, these are summarized in backendError.