sevDesk icon

sevDesk

Consume the sevDesk API

Actions98

Invoice Position → Get Many

AI-generated

Overview

This node interacts with the sevDesk API to retrieve multiple invoice positions based on specified filters and limits. It is useful for scenarios where you need to fetch detailed line items (positions) from invoices, such as generating reports, syncing invoice data with other systems, or performing bulk analysis of invoice contents.

For example, you can use this node to:

  • Retrieve all positions related to a specific invoice by its ID.
  • Fetch positions associated with a particular part ID.
  • Limit the number of returned positions for performance or pagination purposes.

Properties

Name Meaning
Return All Whether to return all matching invoice positions or only up to a specified limit.
Limit Maximum number of invoice positions to return when "Return All" is false.
Filters Criteria to filter the invoice positions:
   Invoice ID Filter positions belonging to a specific invoice by its ID.
   Part ID Filter positions related to a specific part by its ID.

Output

The node outputs an array of JSON objects representing the invoice positions retrieved from the sevDesk API. Each object corresponds to one invoice position and contains fields as defined by the sevDesk API response for invoice positions.

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 produced by this node.

Dependencies

  • Requires an active connection to the sevDesk API via an API key credential.
  • 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.
  • No additional external dependencies beyond the sevDesk API and n8n's credential system.

Troubleshooting

  • Common issues:
    • Invalid or missing API authentication token will cause authorization failures.
    • Providing invalid invoice or part IDs in filters may result in empty results.
    • Exceeding API rate limits could lead to request failures.
  • Error messages:
    • Errors thrown by the API or network issues are caught and can be output if "Continue On Fail" is enabled.
    • Typical error messages include authorization errors, invalid parameters, or server errors.
  • Resolutions:
    • Verify API credentials and permissions.
    • Double-check filter values for correctness.
    • Use "Return All" carefully to avoid large data requests that might time out.

Links and References

Discussion