Actions30
Overview
This node integrates with the MoySklad API v1.2 to manage supply entities within the MoySklad system. Specifically, the Update Supply operation allows users to modify existing supply records by specifying the supply ID and providing updated data in JSON format.
Common scenarios for this node include:
- Updating details of a supply order such as quantities, dates, or linked documents.
- Adjusting supply metadata after initial creation to reflect changes in business processes.
- Automating supply updates based on external triggers or workflows.
For example, a user might automate updating a supply's status or attributes after receiving confirmation from a warehouse management system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the supply entity to update. |
| Body | Raw JSON object containing the fields and values to update on the supply entity, following API schema. |
| Additional Options | Optional parameters to refine the request: |
| - Expand | Comma-separated list of related entities to expand in the response (e.g., linked documents). |
| - Filters | Semicolon-separated filters to apply when querying (supports custom fields, e.g., attributes.name=value). |
| - Limit | Maximum number of items to return (default 100, min 1, max 1000). |
| - Offset | Number of items to skip before starting to collect the result set (default 0). |
Output
The output is a JSON object representing the updated supply entity as returned by the MoySklad API. It reflects the current state of the supply after applying the update.
Example structure (simplified):
{
"id": "string",
"name": "string",
"moment": "datetime",
"positions": [...],
"state": {...},
...
}
No binary data output is produced by this operation.
Dependencies
- Requires an API token credential for authenticating with the MoySklad API.
- The node uses the official MoySklad REST API endpoint at
https://api.moysklad.ru/api/remap/1.2. - Network connectivity to MoySklad API must be available.
- No additional external libraries beyond Axios (bundled) are required.
Troubleshooting
- Missing API credentials: The node will throw an error if the API token is not provided or invalid. Ensure the API key credential is configured correctly.
- HTTP errors (status >= 400): The node surfaces detailed error messages from the MoySklad API. Common causes include invalid IDs, malformed JSON body, or insufficient permissions.
- Rate limiting (HTTP 429): The node implements retry logic with exponential backoff. If requests continue to fail due to rate limits, consider reducing request frequency.
- Invalid JSON in Body: Ensure the JSON string provided in the Body property is valid and matches the expected schema for the supply entity.
- Incorrect ID: Providing a non-existent or incorrect supply ID will cause a 404 or similar error from the API.