Actions30
Overview
This node integrates with the MoySklad API v1.2 to manage entities such as Counterparties, Products, Orders, and more. Specifically, for the Counterparty - Update Status operation, it allows users to update the status of a counterparty entity by sending a raw JSON body describing the new status.
Typical use cases include:
- Automating status changes of counterparties in your inventory or CRM system.
- Synchronizing counterparty statuses between MoySklad and other business tools.
- Bulk updating statuses based on external triggers or workflows.
For example, you might use this node to mark a counterparty as "inactive" after a certain period of inactivity or to update their verification status following an external compliance check.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the counterparty to update. Required for operations that target a specific entity. |
| Body | Raw JSON payload according to the MoySklad API specification. This should contain the status update details. |
| Additional Options | A collection of optional parameters: • Expand: Comma-separated related entities to expand in the response. • Filters: Semicolon-separated filters supporting custom fields (e.g., attributes.name=value). • Limit: Number limiting the number of returned items (1–1000). • Offset: Number specifying the offset for pagination (minimum 0). |
Output
The node outputs JSON data representing the updated counterparty entity as returned by the MoySklad API after the status update. The structure corresponds directly to the API's response, including all fields of the updated entity.
If the operation fails, the node throws an error with the HTTP status code and the error message from the API.
No binary data output is produced by this operation.
Dependencies
- Requires a valid MoySklad API token credential configured in n8n.
- Network access to
https://api.moysklad.ru/api/remap/1.2. - The node uses Axios for HTTP requests with built-in retry logic for rate limiting (HTTP 429).
Troubleshooting
- Missing Credentials Error: If the node throws "Missing MoySklad API credentials," ensure that a valid API token credential is set up in n8n.
- API Errors (Status >= 400): The node surfaces errors returned by the MoySklad API, including validation errors or permission issues. Check the error message for details.
- Rate Limiting (HTTP 429): The node automatically retries requests when rate limited, but excessive calls may still fail. Reduce request frequency or increase limits if possible.
- Invalid JSON in Body: Ensure the "Body" property contains valid JSON matching the API schema; otherwise, parsing errors or API rejections will occur.
- Incorrect ID: Providing an invalid or non-existent counterparty ID will result in a 404 or similar error from the API.