sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node interacts with the sevDesk API to retrieve multiple credit note positions ("Credit Note Po"). Specifically, the "Get Many" operation fetches a list of credit note positions filtered by certain criteria. This is useful in scenarios where you want to gather detailed line items or positions associated with one or more credit notes for accounting, auditing, or reporting purposes.

Practical examples include:

  • Retrieving all positions related to a specific credit note to analyze returned goods or services.
  • Aggregating credit note positions for financial reconciliation or export to other systems.
  • Filtering credit note positions by credit note ID to display or process only relevant entries.

Properties

Name Meaning
Filters Collection of filters to narrow down the credit note positions retrieved. Options:
- Credit Note ID (creditNote[id]) The unique identifier of the credit note whose positions you want to retrieve. Must be provided together with the Credit Note Object Name.
- Credit Note Object Name (creditNote[objectName]) The object name corresponding to the credit note, defaulting to "CreditNote". Required if Credit Note ID is provided.

Output

The node outputs an array of JSON objects representing the credit note positions that match the specified filters. Each item corresponds to a single credit note position with its details as returned by the sevDesk API.

If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs error information in the json.error field alongside the paired input item index.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The base URL for API requests is https://my.sevdesk.de/api/ with a version segment dynamically set from credentials.
  • Environment configuration validation is performed before execution.
  • Uses internal resource manager logic to handle API calls and operations.

Troubleshooting

  • Common issues:
    • Missing or incorrect API authentication token will cause request failures.
    • Providing a Credit Note ID without the corresponding Object Name may result in no data returned or errors.
    • Network connectivity problems can prevent successful API communication.
  • Error messages:
    • Errors thrown by the API or network issues are caught and can be output as error messages if "Continue On Fail" is enabled.
    • Validation schema initialization failure logs an error on startup but does not stop node execution.

To resolve these:

  • Ensure valid API credentials are configured.
  • Provide both Credit Note ID and Object Name when filtering.
  • Check network access to sevDesk API endpoints.
  • Enable "Continue On Fail" to capture and handle errors gracefully within workflows.

Links and References

Discussion