Actions34
- Сборочные Задания Actions
- Метаданные Actions
- Поставки FBS Actions
- Post Supplies
- Get Supplies
- Patch Supplies Orders By Supplyid By Orderid
- Get Supplies By Supplyid
- Delete Supplies By Supplyid
- Get Supplies Orders By Supplyid
- Patch Supplies Deliver By Supplyid
- Get Supplies Barcode By Supplyid
- Get Supplies Trbx By Supplyid
- Post Supplies Trbx By Supplyid
- Delete Supplies Trbx By Supplyid
- Patch Supplies Trbx By Supplyid By Trbxid
- Delete Supplies Trbx Orders By Supplyid By Trbxid By Orderid
- Post Supplies Trbx Stickers By Supplyid
- Пропуска Actions
- Доставка Курьером WB DBW Actions
Overview
This node interacts with the "Сборочные Задания" (Assembly Tasks) resource of an API to retrieve orders. It is designed to fetch paginated order data within a specified date range, making it useful for workflows that need to process or analyze batches of orders from this resource.
Typical use cases include:
- Automating order retrieval for reporting or analytics.
- Integrating order data into other systems or databases.
- Monitoring new or updated orders over time.
For example, you could configure the node to fetch all orders created in the last 30 days, processing them in chunks using pagination parameters.
Properties
| Name | Meaning |
|---|---|
| Limit | Pagination parameter that sets the maximum number of orders to return in one request. |
| Next | Pagination parameter indicating the starting point for the next batch of data. For the first request, set to 0; subsequent requests should use the value returned in the response's next field. |
| Date From | Start date of the period to fetch orders, expressed as a Unix timestamp. Defaults to 30 days before the current date if not set. |
| Date To | End date of the period to fetch orders, expressed as a Unix timestamp. |
Output
The node outputs JSON data containing the retrieved orders. The structure includes:
- An array of order objects representing individual orders fetched from the API.
- A
nextfield indicating the cursor or offset to be used for fetching the next page of results.
No binary data output is indicated by the source code.
Dependencies
- Requires connection to the external API providing the "Сборочные Задания" resource.
- Needs an API authentication token or key configured in n8n credentials (referred generically as an API key credential).
- The base URL and API schema are derived from a bundled OpenAPI specification file (
03-orders-fbs_modified.json).
Troubleshooting
- Pagination issues: If the
nextparameter is not managed correctly (e.g., not updated with the response'snextvalue), the node may repeatedly fetch the same data or miss some orders. - Date format errors: Ensure
dateFromanddateToare valid Unix timestamps; otherwise, the API might reject the request or return no data. - Limit parameter: Setting
limitto 0 might result in no data being returned or default server behavior; verify the API documentation for acceptable values. - Authentication failures: Missing or invalid API credentials will cause authorization errors. Verify that the API key credential is properly configured in n8n.
- Network or API errors: Handle common HTTP errors such as 429 (rate limiting) or 500 (server errors) by implementing retry logic or error handling in your workflow.
Links and References
- No direct links were provided in the source code or properties.
- Refer to the official API documentation of the "Сборочные Задания" resource for detailed information on parameters and response formats.
- n8n documentation on pagination and API integrations may help in configuring and troubleshooting this node.