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 → Interested Parties Actions
AI-generatedSummary
Get the MS Manual interested parties data or submit updated data for an ISO engagement. Select Get Interested Parties or Set Interested Parties to issue the corresponding request to the MSFrog API.
Inputs
- Action (required) — Choose Get Interested Parties (GET /intparts) or Set Interested Parties (POST /intparts).
- ISO Engagement ID (required) — Identifies the ISO engagement in the request path.
- Body (JSON) — JSON payload sent by Set Interested Parties; ignored by the GET action.
- Base URL Override — Overrides the base URL from the MSFrog credentials for this node.
Output shape
One n8n item per input item, containing the API response as JSON with request metadata.
The output includes operation, route value, engagement ID, HTTP method, full path, route parameters, and request body alongside the response. The body defaults to an empty object; the response is also available under response. API results containing error, details, or err_code include those fields under backendError.