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 → USPs Actions
AI-generatedSummary
Retrieve the MS Manual’s USPs or submit a new USPs payload for a specified ISO engagement. Choose Get USPS to make a GET request or Set USPS to make a POST request to the engagement’s /msmanual/usps endpoint.
Inputs
- ISO Engagement ID (required) — Engagement ID used to build the API path.
- Action (required) — Choose Get USPS (GET) or Set USPS (POST).
- Body (JSON) — JSON request payload used by Set USPS; ignored by Get USPS.
- Base URL Override — Overrides the base URL from credentials for this node. If omitted, the credential base URL is used, with a built-in fallback if that is also absent.
Output shape
A list of n8n items, with one item per input item.
Each item contains the API result merged with request metadata, including the selected route, engagement ID, method, path, route parameters, and body. If the API result includes error-related fields, a backendError object is included. Get USPS requires no route parameters.
Examples
Example 1: Get USPS
Set Action to Get USPS and provide the ISO Engagement ID.
Example 2: Set USPS
Set Action to Set USPS, provide the ISO Engagement ID, and enter the payload in Body (JSON).