Actions20
- Вопросы Actions
- Отзывы Actions
- Шаблоны Ответов Actions
- Чат С Покупателями Actions
- Возвраты Покупателями Actions
Overview
This node allows updating (patching) claims related to customer returns ("Возвраты Покупателями") in a system, likely an e-commerce or order management platform. It is useful for managing the status and details of return requests submitted by customers. For example, you can approve or reject a claim with a custom comment explaining the reason.
Typical use cases include:
- Rejecting a return claim with a specific reason.
- Approving a claim after review.
- Adding comments to clarify the action taken on a claim.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the claim to be updated. |
| Action | The action to perform on the claim. Must be one of the predefined values from the actions array returned by the "get claims" method. Examples include rejectcustom, approvecc1, etc. |
| Comment | A comment explaining the action. Required if the action is rejectcustom. Also applicable when action is approvecc1. Example: "Фото не имеет отношения к товару в заявке" (The photo is not related to the product in the claim). |
Output
The node outputs JSON data representing the updated claim after the patch operation. This typically includes the claim's current status, any comments added, and other relevant metadata reflecting the update.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests to the external service managing customer return claims.
- The node uses a base URL and OpenAPI specification bundled internally to construct requests.
- No additional environment variables are explicitly required beyond standard API authentication setup.
Troubleshooting
- Missing or invalid claim ID: Ensure the
Idproperty is correctly set to a valid claim identifier; otherwise, the API will reject the request. - Invalid action value: The
Actionmust be one of the allowed strings from the service’s documented actions list. Using an unsupported action will cause errors. - Missing comment when required: If the action is
rejectcustom, theCommentfield is mandatory. Omitting it will result in an error. - API authentication errors: Verify that the API key or token is correctly configured in n8n credentials.
- Network or service errors: Check connectivity and service availability if requests fail unexpectedly.
Links and References
- API documentation for Возвраты Покупателями claims (referenced for valid actions)
- General n8n documentation on creating and using HTTP Request nodes and API integrations.