sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node interacts with the sevDesk API to perform various operations on different resources. Specifically, for the Contact resource and the Is Deletable operation, it checks whether a given contact can be deleted from the sevDesk system. This is useful in scenarios where you want to programmatically verify if a contact is eligible for deletion before attempting to remove it, preventing errors or data integrity issues.

Practical examples include:

  • Automating cleanup of contacts by first verifying deletability.
  • Integrating with other systems to sync contact status and safely delete contacts.
  • Building workflows that conditionally delete contacts only if they are deletable.

Properties

Name Meaning
Contact ID The unique identifier of the contact to check. Required to specify which contact to query.

Output

The node outputs JSON data indicating whether the specified contact is deletable. The exact structure depends on the API response but generally includes a boolean or status field confirming deletability.

If an error occurs (e.g., invalid Contact ID or API failure), the output JSON will contain an error field with the error message.

No binary data output is involved.

Dependencies

  • Requires an active connection to the sevDesk API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node uses the base URL https://my.sevdesk.de/api/ combined with the API version from credentials.
  • Environment configuration validation is performed at runtime to ensure proper setup.

Troubleshooting

  • Common Issues:

    • Invalid or missing Contact ID will cause the operation to fail.
    • Network or authentication errors if the API key is incorrect or expired.
    • API rate limits or permission restrictions may prevent successful execution.
  • Error Messages:

    • Errors returned from the API are passed through in the output under an error field.
    • If the node is set to continue on failure, errors for individual items do not stop the workflow but are reported per item.
  • Resolutions:

    • Verify the Contact ID exists and is correctly formatted.
    • Check API credentials and permissions.
    • Ensure network connectivity to sevDesk API endpoints.
    • Review API usage limits and adjust workflow frequency accordingly.

Links and References

Discussion