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 → Supplier Evaluation Actions
AI-generatedSummary
Manage supplier types and supplier evaluations for an ISO engagement. Choose an action to retrieve or update supplier data, mark an evaluation complete or incomplete, or delete a supplier type or evaluation.
Inputs
- Base URL Override — Optional base URL that overrides the one in the MSFrog credentials for this node.
- Action (required) — Select Get Supplier Types, Set Supplier Types, Delete Supplier Type, Get Supplier Evaluation, Get Used Supplier Types, Set Supplier Evaluation, Complete Supplier Evaluation, Incomplete Supplier Evaluation, or Delete Supplier Evaluation.
- ISO Engagement ID (required) — ISO engagement ID used to build the MS Manual API request path.
- Route Params (JSON) — JSON object supplying path placeholders. Delete Supplier Type requires
sullpiertypeId; Delete Supplier Evaluation requiressuppevId. Placeholder values are URL-encoded. - Body (JSON) — Request payload for Set Supplier Types and Set Supplier Evaluation. Other actions do not send this body.
Output shape
One n8n item per input item, containing the API result in its JSON data, augmented with request metadata.
The output includes operation, selected route, ISO engagement ID, HTTP method, full path, route parameters, body (or an empty object), and response. If the API result contains
error,details, orerr_code, these are also summarized underbackendError; otherwise it is null. Invalid JSON, missing required path parameters, or request errors fail the item unless Continue On Fail is enabled, in which case an item with anerrorfield is returned.