Actions41
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Actions
- ContactAddress Actions
- Invoice Actions
- Part Actions
Overview
This node integrates with the sevDesk API to manage various resources, including Communication Ways. Specifically, the "Delete" operation for the CommunicationWay resource allows users to remove a communication method (such as an email address or phone number) identified by its unique ID from their sevDesk account.
Common scenarios include cleaning up outdated or incorrect contact information associated with customers or vendors in sevDesk. For example, if a phone number is no longer valid, this node can be used to delete that communication way to keep records accurate.
Properties
| Name | Meaning |
|---|---|
| Communication Way ID | Unique identifier of the Communication Way to be deleted. This is a required numeric ID. |
Output
The node outputs JSON data representing the response from the sevDesk API after attempting to delete the specified Communication Way. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If the API supports binary data output for this operation (unlikely for a delete), it would represent related files or attachments, but based on the static code and typical REST API behavior, only JSON responses are expected.
Dependencies
- Requires an active connection to the sevDesk API.
- Users must provide valid API authentication credentials (an API key or token) configured within n8n.
- The base URL for API requests is
https://my.sevdesk.de/api/v1/.
Troubleshooting
- Invalid Communication Way ID: If the provided ID does not exist or is incorrect, the API will return an error indicating the resource was not found. Verify the ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly set up in n8n credentials.
- Network Issues: Connectivity problems may prevent the node from reaching the sevDesk API. Check network settings and firewall rules.
- Permission Denied: The API user might lack permissions to delete communication ways. Confirm the API user's access rights in sevDesk.
Links and References
- sevDesk API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of HTTP and API nodes)