MoySklad

Interact with MoySklad API v1.2

Actions30

Overview

This node integrates with the MoySklad API v1.2, enabling users to manage various resources such as products, customer orders, counterparties, supplies, and demands. Specifically, for the Demand - Create operation, it allows creating new demand records in MoySklad by sending a raw JSON body that conforms to the API's expected format.

Common scenarios where this node is beneficial include automating inventory or order management workflows, syncing demand data from other systems into MoySklad, or programmatically generating demand entries based on business logic.

Example use case: Automatically create a demand record when a customer places an order on an e-commerce platform, by passing the order details as JSON to this node.

Properties

Name Meaning
Body Raw JSON body representing the demand to create, formatted according to the MoySklad API requirements.
Additional Options Collection of optional parameters:
- Expand Comma-separated list of related entities to expand in the response (e.g., linked documents or metadata).
- Filters Semicolon-separated filters to apply when querying (not typically used in create but available).
- Limit Maximum number of items to return when applicable (default 100, range 1-1000).
- Offset Number of items to skip when paginating results (default 0).

Output

The output is a JSON object containing the newly created demand entity as returned by the MoySklad API. This includes all fields of the demand resource, potentially expanded relations if requested.

Example structure (simplified):

{
  "id": "string",
  "name": "string",
  "moment": "datetime",
  "positions": [...],
  "state": {...},
  ...
}

No binary data output is produced by this node.

Dependencies

  • Requires an API authentication token credential for MoySklad.
  • Uses the official MoySklad REST API endpoint https://api.moysklad.ru/api/remap/1.2.
  • The node handles HTTP requests with automatic retry on rate limiting (HTTP 429).
  • Timeout for API calls is set to 60 seconds.

Troubleshooting

  • Missing credentials error: If the API token is not provided or invalid, the node will throw an error indicating missing credentials.
  • MoySklad API errors: Any HTTP status code >= 400 from the API will cause the node to throw an error with the status code and response body. Common causes include malformed JSON in the Body property or invalid field values.
  • Rate limiting: The node automatically retries requests on HTTP 429 responses with exponential backoff up to 6 attempts. Persistent rate limiting may require reducing request frequency.
  • JSON parsing errors: Ensure the Body property contains valid JSON. Invalid JSON will cause runtime errors.
  • Incorrect resource or operation: Using unsupported combinations of resource and operation will result in no action or errors.

Links and References

Discussion