sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions98

Overview

This node integrates with the sevDesk API to manage various resources, including check accounts. Specifically, for the CheckAccount resource and the Create Clearing Account operation, it allows users to create a new clearing account in their sevDesk accounting system. This is useful for automating bookkeeping tasks where clearing accounts are needed to temporarily hold funds during transactions.

Practical examples include:

  • Automatically creating clearing accounts when onboarding new clients or projects.
  • Setting up accounts for file imports or batch processing of financial data.
  • Streamlining accounting workflows by programmatically managing account structures.

Properties

Name Meaning
Name The name of the clearing account to be created.
Accounting Number The booking account number used for this clearing account (i.e., the linked ledger).

These properties are required inputs when creating or updating clearing accounts.

Output

The node outputs an array of JSON objects representing the results of the executed operations. Each item corresponds to one input item processed and contains the response from the sevDesk API for that operation.

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

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The base URL for API requests is https://my.sevdesk.de/api/ followed by the API version specified in credentials.
  • Validation schemas are initialized at runtime to ensure request correctness.
  • Environment configuration validation is performed before execution.

Troubleshooting

  • Common issues:

    • Missing or invalid API authentication token can cause authorization failures.
    • Incorrect or missing required properties (Name, Accounting Number) will result in validation errors.
    • Network connectivity problems may prevent successful API calls.

  • Error handling:

    • If "Continue On Fail" is disabled, the node will stop execution on the first error.
    • If enabled, errors for individual items are captured in the output with an error message field.
    • Initialization failure of validation schemas logs an error to the console but does not halt execution.

Links and References

Discussion