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 → Terms and Definitions Actions
AI-generatedSummary
Manage terms and definitions for an ISO engagement: retrieve them, submit a JSON payload, mark them complete or incomplete, or delete a definition by UUID.
Inputs
- Base URL Override — Optional base URL that overrides the URL in MSFrog credentials for this node.
- Action (required) — Choose Get Terms Definitions (GET), Set Terms Definitions (POST), Complete Terms Definitions (PUT), Incomplete Terms Definitions (PUT), or Delete Terms Definitions (DELETE).
- ISO Engagement ID (required) — Engagement ID used to build the MS Manual API path.
- Route Params (JSON) — JSON object supplying route placeholders. For Delete Terms Definitions, provide the required
uuid. - Body (JSON) — Request payload for routes that accept a body, including Set Terms Definitions. It is ignored for GET and routes without a body.
Output shape
A list of n8n items, one per input item, each containing the API result as JSON.
Each result is enriched with the selected operation, route value, engagement ID, HTTP method, full request path, route parameters, and request body; it also includes a
responsefield and abackendErrorfield, which is populated when the result contains error details. Route placeholders are URL-encoded. Missing required placeholders or invalid JSON cause an operation error unless Continue On Fail is enabled, in which case an error item is returned.