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 Orders. Specifically, for the Order - Delete operation, it allows users to delete an existing order by specifying its unique Order ID. This is useful in scenarios where orders need to be removed from the system due to cancellation, errors, or data cleanup.
Practical examples:
- Automatically deleting orders that were canceled in an external system.
- Cleaning up test or duplicate orders during data synchronization workflows.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to delete. This is a required string input property. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any error messages returned by the sevDesk API.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message for the corresponding item.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the sevDesk API.
- The base URL for API requests is
https://my.sevdesk.de/api/followed by the API version specified in credentials. - Environment configuration validation is performed before execution.
Troubleshooting
Common issues:
- Invalid or missing Order ID will cause the API to reject the request.
- Authentication failures if the API key credential is incorrect or expired.
- Network connectivity problems preventing access to the sevDesk API endpoint.
Error messages:
- Errors returned from the API are captured and can be output per item if "Continue On Fail" is enabled.
- Typical error messages might include "Order not found" or "Unauthorized".
Resolution tips:
- Verify the Order ID exists and is correct.
- Check API credentials and permissions.
- Ensure network connectivity and API endpoint availability.
Links and References
- sevDesk API Documentation (official API docs for reference)
- n8n documentation on creating custom nodes