sevDesk icon

sevDesk

Consume the sevDesk API

Overview

The node integrates with the sevDesk API to retrieve multiple voucher records based on specified filters. It is useful for scenarios where users need to fetch a list of vouchers matching certain criteria such as date ranges, status, or associated contacts. For example, an accountant might use this node to pull all open credit vouchers for a specific client within a given time period to reconcile accounts.

Properties

Name Meaning
Filters A collection of optional filters to narrow down the vouchers retrieved:
- Contact ID Filter vouchers by the associated contact's unique identifier (string).
- Credit/Debit Choose whether to retrieve Credit ("C") or Debit ("D") vouchers.
- Description Filter vouchers containing a specific description text (string).
- End Date Timestamp representing the upper bound of the voucher date range.
- Start Date Timestamp representing the lower bound of the voucher date range.
- Status Filter vouchers by their status: Draft (50), Open (100), or Paid (1000).

Output

The node outputs an array of JSON objects, each representing a voucher that matches the filter criteria. Each object contains the voucher data as returned by the sevDesk API. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The base URL for API requests is https://my.sevdesk.de/api/ appended with the API version from credentials.
  • Environment configuration validation is performed before execution.

Troubleshooting

  • Common issues:
    • Invalid or missing API authentication token will cause request failures.
    • Incorrect filter values (e.g., invalid timestamps or unsupported status codes) may result in empty responses or errors.
  • Error handling:
    • If an error occurs during fetching vouchers, and "Continue On Fail" is enabled, the node returns an error object for that item instead of stopping execution.
    • Error messages typically contain the reason for failure, such as network issues or invalid parameters.
  • Resolution tips:
    • Verify API credentials are correctly configured.
    • Ensure filter values conform to expected formats and valid options.
    • Use "Continue On Fail" cautiously to handle partial failures gracefully.

Links and References

Discussion