sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API to perform various operations on sevDesk resources. Specifically, for the Tag resource with the Delete operation, it allows users to delete a tag by specifying its ID. This is useful in scenarios where tags are used to categorize or label entities within sevDesk and need to be removed when they become obsolete or incorrect.

Practical examples:

  • Removing outdated or duplicate tags from your accounting system.
  • Cleaning up tags that were created by mistake or are no longer relevant.

Properties

Name Meaning
ID The unique identifier of the tag to delete. This 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. If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

No binary data output is involved in 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 required environment variables or settings are correct.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent tag ID will cause the delete operation to fail.
    • Missing or incorrect API authentication credentials will prevent successful API calls.
    • Network connectivity issues can cause request failures.
  • Error messages:

    • Errors returned from the API will be included in the output JSON under an error property if "Continue On Fail" is enabled.
    • Common errors include "Tag not found" or "Unauthorized" due to invalid credentials.
  • Resolutions:

    • Verify the tag ID exists in sevDesk before attempting deletion.
    • Ensure the API key credential is correctly configured and has sufficient permissions.
    • Check network connectivity and retry if necessary.

Links and References

Discussion