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 → Normative References Actions
AI-generatedSummary
Manage normative references for an ISO engagement: retrieve the list or one reference, create or update a reference, mark references complete or incomplete, or delete one.
Inputs
- Base URL Override — Optionally overrides the Base URL in the MSFrog credentials for this node.
- Action (required) — Select Get Norm Refs, Get Norm Ref, Create Norm Ref, Complete Norm Ref, Incomplete Norm Ref, Update Norm Ref, or Delete Norm Ref.
- ISO Engagement ID (required) — Identifies the ISO engagement whose MS Manual normative references are affected.
- Route Params (JSON) — Supply path parameters as JSON. Get Norm Ref, Update Norm Ref, and Delete Norm Ref require normRefId.
- Body (JSON) — JSON payload for Create Norm Ref and Update Norm Ref; ignored by GET actions. The source does not specify the payload fields.
Output shape
One n8n item per input item, containing the API result with request metadata.
The output JSON includes operation, selected route, engagement ID, HTTP method, full path, route parameters, request body (or an empty object), and the API response. If the result contains error, details, or err_code fields, these are also summarized in backendError; otherwise backendError is null. Missing required route parameters and invalid JSON inputs cause errors unless Continue On Fail is enabled.