sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API to manage check account transactions. Specifically, the "Update" operation for the "CheckAccountTransaction" resource allows users to modify existing check account transaction records by specifying their ID and updating fields such as amount, payee/payer name, payment purpose, and status.

Common scenarios include:

  • Updating transaction details after receiving new information or corrections.
  • Changing the status of a transaction to reflect its current state in accounting workflows.
  • Adjusting amounts or payee names due to bookkeeping updates.

Practical example:
A user wants to update a check transaction's amount and mark it as "booked" after confirming the payment cleared the bank.

Properties

Name Meaning
Check Account Transaction ID The unique identifier of the check account transaction to update. Required for update and delete operations.
Amount The monetary value of the transaction. Must be a number.
Payee/Payer Name The name of the person or entity who is paying or being paid in the transaction.
Payment Purpose A description or reason for the payment.
Status The current state of the transaction. Options: Created, Linked, Private, Booked.

Output

The node outputs an array of JSON objects representing the response from the sevDesk API after performing the update operation on the check account transaction. Each output item corresponds to one input item processed.

The json field contains the updated transaction data returned by the API. If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

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/{apiVersion}, where {apiVersion} is specified in the credentials.
  • Environment configuration validation is performed before execution.

Troubleshooting

  • Common issues:

    • Invalid or missing Check Account Transaction ID will cause the update to fail.
    • Providing invalid values for required fields (e.g., non-numeric amount) may result in API errors.
    • Network or authentication failures if the API key is incorrect or expired.
  • Error messages:

    • Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
    • Validation warnings or errors related to environment configuration may appear if setup is incomplete.
  • Resolutions:

    • Ensure all required properties are correctly set.
    • Verify API credentials and network connectivity.
    • Use "Continue On Fail" cautiously to handle partial failures gracefully.

Links and References

Discussion