sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API, allowing users to perform various operations on sevDesk resources. Specifically, for the "Part" resource and the "Get Stock" operation, it retrieves stock information about a specific part identified by its Part ID. This is useful in inventory management scenarios where you need to check current stock levels of parts or products within sevDesk.

Practical examples include:

  • Automatically fetching stock levels before creating orders.
  • Monitoring inventory changes by periodically retrieving stock data.
  • Integrating stock information into other workflows like alerts or reporting.

Properties

Name Meaning
Part ID The unique identifier of the part whose stock information you want to retrieve. This is a required string input.

Output

The node outputs JSON data containing the stock details of the specified part. The exact structure depends on the sevDesk API response but typically includes fields such as available quantity, reserved stock, and other relevant stock metrics.

If the node encounters an error (e.g., invalid Part ID), the output JSON will contain an error field describing the issue.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the sevDesk API via an API key credential configured in n8n.
  • The node uses the base URL https://my.sevdesk.de/api/ combined with the API version specified in credentials.
  • Environment configuration validation is performed at runtime to ensure proper setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Part ID will cause errors.
    • Network connectivity problems or incorrect API credentials can lead to authentication failures.
    • If the API version in credentials is outdated or unsupported, requests may fail.
  • Error messages:

    • Errors returned from the API are passed through in the output JSON under an error property.
    • Initialization errors related to validation schemas are logged to the console but do not stop execution.
  • Resolutions:

    • Verify that the Part ID is correct and exists in sevDesk.
    • Ensure API credentials are valid and have necessary permissions.
    • Check network connectivity and API endpoint accessibility.
    • Confirm environment variables and configurations meet requirements.

Links and References

Discussion