Actions98
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact 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
- Invoice Actions
- Invoice Position Actions
- Order Actions
- Order Position Actions
- Part Actions
- Report Actions
- Tag Actions
- Voucher Actions
- VoucherPo Actions
CheckAccountTransaction → Delete
AI-generatedOverview
This node integrates with the sevDesk API to manage financial data. Specifically, the "CheckAccountTransaction" resource with the "Delete" operation allows users to delete a specific check account transaction by its ID. This is useful for scenarios where erroneous or outdated transactions need to be removed from the accounting records.
Practical examples include:
- Removing duplicate transactions imported by mistake.
- Deleting test transactions created during system setup.
- Cleaning up transactions that were entered incorrectly and cannot be edited.
Properties
| Name | Meaning |
|---|---|
| Check Account Transaction ID | The unique identifier of the check account transaction to delete. This is required. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If an error occurs and the node is configured to continue on failure, the output JSON will contain an error field with the error message.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with 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.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Check Account Transaction ID will cause the API to return an error.
- Missing or incorrect API authentication credentials will prevent the node from connecting to sevDesk.
- Network connectivity problems can cause request failures.
Error messages:
- Errors returned from the API are passed through in the output JSON under the
errorfield if "Continue On Fail" is enabled. - Typical errors include "Not Found" if the transaction ID does not exist, or "Unauthorized" if credentials are invalid.
- Errors returned from the API are passed through in the output JSON under the
Resolution tips:
- Verify the transaction ID is correct and exists in sevDesk.
- Ensure the API key credential is properly configured and has necessary permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- sevDesk API Documentation
- n8n documentation on creating custom nodes