Actions30
Overview
This node integrates with the MoySklad API v1.2 to manage various resources, including Customer Orders. Specifically, the Delete operation for the Customer Order resource allows users to remove a customer order by its unique ID.
Typical use cases include:
- Automating cleanup of obsolete or erroneous customer orders.
- Integrating with other systems where order cancellation or deletion is required.
- Managing order lifecycle programmatically within workflows.
For example, you might use this node in an automation that deletes customer orders marked as duplicates or cancelled in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the Customer Order to delete. Required for delete operation. |
| Additional Options | A collection of optional parameters: |
| - Expand | Comma-separated list of related entities to expand in the response (not typically used in delete). |
| - Filters | Semicolon-separated filters to narrow down results (not applicable for delete but available for other ops). |
| - Limit | Maximum number of items to return (default 100, max 1000). Not applicable for delete operation. |
| - Offset | Number of items to skip before starting to collect the result set (default 0). Not applicable for delete. |
Note: For the Delete operation on Customer Order, only the ID property is strictly required and used. Additional options are generally irrelevant for deletion but exist as part of the node's general interface.
Output
The output JSON for a successful delete operation contains:
{
"success": true,
"id": "<deleted_customer_order_id>"
}
success: Boolean indicating the deletion was successful.id: The ID of the deleted Customer Order.
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for MoySklad API authentication.
- The node uses the official MoySklad REST API endpoint at
https://api.moysklad.ru/api/remap/1.2. - Network connectivity to MoySklad API is necessary.
- No additional external dependencies beyond Axios HTTP client bundled internally.
Troubleshooting
- Missing Credentials Error: If the API token is not provided or invalid, the node will throw an error "Missing MoySklad API credentials". Ensure valid API token credentials are configured in n8n.
- HTTP Errors: Any HTTP status code >= 400 from the API will cause an error with details, e.g.,
MoySklad error 404: {...}. Common causes:- Invalid or non-existent Customer Order ID.
- Insufficient permissions for the API token.
- Network issues or API downtime.
- Rate Limiting: The node implements retry logic on HTTP 429 responses with exponential backoff. However, excessive requests may still fail; consider reducing request frequency.
- Invalid ID Format: Ensure the ID provided matches the expected format used by MoySklad.