sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API to retrieve multiple voucher purchase order positions ("VoucherPo"). It is designed to fetch many entries at once, optionally filtered by specific criteria such as a Voucher ID. This functionality is useful for accounting and finance automation workflows where users need to gather detailed position data related to vouchers in bulk.

Practical examples include:

  • Retrieving all purchase order positions linked to a particular voucher for reconciliation.
  • Extracting multiple voucher positions to generate reports or export data.
  • Automating bookkeeping tasks by fetching voucher details programmatically.

Properties

Name Meaning
Filters Collection of filters to narrow down the results. Currently supports:
  Voucher ID The ID of the voucher to get positions for. Use this to fetch positions related to a specific voucher.

Output

The node outputs an array of JSON objects representing voucher purchase order positions retrieved from the sevDesk API. Each item corresponds to one voucher position entry with its associated data fields as returned by the API.

If an error occurs during execution for a particular input item and "Continue On Fail" is enabled, the output will include an object with an error field describing the issue for that item.

No binary data output is produced by this node.

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 specified in credentials.
  • Environment configuration validation is performed before execution to ensure necessary environment variables or settings are correct.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token can cause authorization errors.
    • Providing an incorrect Voucher ID filter may result in empty responses.
    • Network connectivity problems can lead to request failures.
  • Error messages:

    • Errors thrown by the API (e.g., invalid parameters) will be surfaced in the node output if "Continue On Fail" is enabled.
    • Initialization errors related to validation schemas are logged to the console but do not stop node execution.
  • Resolutions:

    • Verify API credentials and permissions.
    • Double-check filter values for correctness.
    • Ensure stable network connection.
    • Review console logs for schema initialization warnings.

Links and References

Discussion