Actions98
- Contact Actions
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Address Actions
- Contact Custom Field Actions
- Contact Custom Field Setting Actions
- Credit Note Actions
- Credit Note Po Actions
- Export Actions
- Update Export Config
- Export DATEV (Deprecated)
- Start DATEV CSV Zip Export
- Start DATEV XML Zip Export
- Generate Download Hash
- Get Progress
- Get Job Download Info
- Export Invoice as CSV
- Export Invoice as Zip
- Export Credit Note as CSV
- Export Voucher as CSV
- Export Voucher as Zip
- Export Transaction as CSV
- Export Contact as CSV
- Part Actions
- Invoice Actions
- Invoice Position Actions
- Order Actions
- Order Position Actions
- Report Actions
- Tag Actions
- Voucher Actions
- VoucherPo Actions
Overview
This node integrates with the sevDesk API to manage various resources, including order positions. Specifically, the "Get Many" operation for the "Order Position" resource retrieves multiple order position entries associated with a given order ID. This is useful in scenarios where you want to fetch all line items or components of a particular order for further processing, reporting, or synchronization with other systems.
Practical examples include:
- Extracting all products or services listed in an order to generate invoices or packing slips.
- Synchronizing order details with external inventory or accounting software.
- Analyzing order composition for business intelligence or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order whose positions (line items) you want to retrieve. |
Output
The node outputs an array of JSON objects representing the order positions retrieved from the sevDesk API. Each object corresponds to one order position and contains detailed information such as product details, quantity, price, and any other metadata provided by the API.
If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs error objects containing the error message alongside the index of the input item that caused the failure.
No binary data output is indicated for this operation.
Dependencies
- Requires a valid API key credential for the sevDesk API.
- The node uses the base URL
https://my.sevdesk.de/api/combined with the API version specified in credentials. - Environment configuration validation is performed before execution to ensure necessary environment variables or settings are correctly set.
Troubleshooting
Common Issues:
- Invalid or missing Order ID: The operation requires a valid order ID; providing an incorrect or empty value will result in errors.
- Authentication failures: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Connectivity issues or sevDesk service interruptions can cause request failures.
Error Messages:
- Errors thrown by the API or network issues are caught and, if "Continue On Fail" is enabled, returned as part of the output with an error message field.
- Typical error messages might include authentication errors, invalid parameters, or rate limiting notices.
Resolution:
- Verify the correctness of the Order ID.
- Check API credentials and permissions.
- Review network connectivity.
- Enable "Continue On Fail" to handle partial failures gracefully.
Links and References
- sevDesk API Documentation
- n8n Documentation on Creating Custom Nodes
- General REST API best practices for error handling and pagination