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 perform various operations on different resources. Specifically, for the CommunicationWay resource with the Delete operation, it allows users to delete a communication way entry identified by its unique ID. This is useful in scenarios where outdated or incorrect communication methods (like phone numbers, emails, or other contact channels) need to be removed from the system.
Practical examples:
- Removing an obsolete email address linked to a contact.
- Deleting a deprecated phone number used for customer communication.
Properties
| Name | Meaning |
|---|---|
| Communication Way ID | Unique identifier of the communication way to be deleted. Must be provided as a string. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or any error messages if the operation failed. The output structure corresponds to the response from the sevDesk API for the delete request.
No binary data output is expected from 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 to ensure necessary environment variables or settings are correctly set.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Communication Way ID will likely cause the API to return an error.
- Missing or incorrect API authentication credentials will prevent successful API calls.
- Network connectivity problems can cause request failures.
Error messages and resolutions:
"error": "Resource not found"— Verify that the Communication Way ID exists and is correct.- Authentication errors — Check that the API key credential is valid and has sufficient permissions.
- Validation warnings — Ensure environment configurations required by the node are properly set.
Links and References
- sevDesk API Documentation (for detailed API endpoints and parameters)
- n8n documentation on creating custom nodes