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 accounting contacts. Specifically, the Delete operation for the AccountingContact resource allows users to remove an existing accounting contact by its unique ID. This is useful in scenarios where outdated or incorrect contact information needs to be purged from the system to maintain data accuracy.
Practical examples include:
- Automatically deleting accounting contacts that are no longer relevant after a client relationship ends.
- Cleaning up test or duplicate contacts during data maintenance workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the accounting contact to delete. This is a required string input. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. For the Delete operation on AccountingContact, the output typically contains confirmation of deletion or any error messages if the operation failed.
json: Contains the response from the API after attempting to delete the specified accounting contact.- If an error occurs and "Continue On Fail" is enabled, the output will include an
errorfield describing the issue for that particular item.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the sevDesk API via an API key credential.
- The node expects the environment configuration to be validated before execution.
- No additional external dependencies beyond the sevDesk API and proper authentication.
Troubleshooting
Common issues:
- Providing an invalid or non-existent accounting contact ID will result in an error from the API.
- Missing or incorrect API credentials will prevent successful communication with sevDesk.
- Network connectivity problems can cause request failures.
Error messages:
- Errors returned from the API will be included in the output under the
errorfield if "Continue On Fail" is enabled. - Typical errors include "Not Found" if the ID does not exist, or "Unauthorized" if credentials are invalid.
- Errors returned from the API will be included in the output under the
Resolutions:
- Verify the accounting contact 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 issues occur.
Links and References
- sevDesk API Documentation
- n8n documentation on creating custom nodes