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 contacts and other related resources. Specifically, for the Contact - Delete operation, it allows users to delete a contact by specifying its unique ID. This is useful in scenarios where outdated or incorrect contact records need to be removed from the sevDesk system to maintain data accuracy.
Practical examples include:
- Automatically cleaning up contacts that are no longer relevant.
- Removing duplicate or test contacts created during data import or testing phases.
- Integrating with workflows that deactivate customers or vendors and subsequently remove their contact information.
Properties
| Name | Meaning |
|---|---|
| Contact ID | ID of the contact to delete |
The "Contact ID" property is required and expects a number representing the unique identifier of the contact to be deleted.
Output
The node outputs JSON data representing the response from the sevDesk API after attempting to delete the contact. Typically, this will include confirmation of deletion or an error message if the operation failed.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the sevDesk API.
- The node must be configured with valid API authentication credentials (an API key or token) to authorize requests.
- Network access to
https://my.sevdesk.de/api/v1/is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will result in an error from the API indicating the contact could not be found.
- Missing or invalid API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the sevDesk API endpoint.
Error messages and resolutions:
- "Contact not found": Verify that the Contact ID is correct and exists in sevDesk.
- "Unauthorized" or "Authentication failed": Check that the API credentials are correctly set up and have sufficient permissions.
- Timeout or network errors: Ensure stable internet connection and that the sevDesk API service is reachable.
Links and References
- sevDesk API Documentation (for detailed API endpoints and responses)
- n8n documentation on creating custom nodes