sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to retrieve multiple "Part" records based on specified filters. It is useful for scenarios where you need to fetch a list of parts from your sevDesk account, such as inventory management, product catalog synchronization, or reporting.

For example, you can use this node to:

  • Retrieve all parts matching a specific part number or name.
  • Paginate through large sets of parts by specifying limits and offsets.
  • Fetch details of a particular part by its ID.

Properties

Name Meaning
Part ID ID of the part to return (fetches a single part by its unique identifier).
Part Number Retrieve all parts that have this exact part number.
Part Name Retrieve all parts that match this name.
Limit Maximum number of results to return (used for pagination).
Offset Number of results to skip before starting to collect the result set (used for pagination).

Output

The node outputs JSON data representing the parts retrieved from the sevDesk API. The structure typically includes an array of part objects, each containing details such as part ID, part number, name, and other relevant attributes defined by the API.

If binary data were involved (e.g., images or files related to parts), it would be included in a separate binary output field, but this operation focuses on JSON data only.

Dependencies

  • Requires an active connection to the sevDesk API.
  • An API authentication token (API key credential) must be configured in n8n to authorize requests.
  • The base URL used for API calls is https://my.sevdesk.de/api/v1/.

Troubleshooting

  • Empty Results: If no parts are returned, verify that the filter criteria (part ID, number, or name) are correct and exist in your sevDesk account.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Pagination Issues: When using limit and offset, ensure values are within valid ranges; otherwise, you might get unexpected empty responses.
  • Invalid Parameter Values: Providing non-numeric values for numeric fields like Part ID, Limit, or Offset may cause errors.

Links and References

Discussion