sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to update a specific Check Account Transaction. It allows users to modify various attributes of an existing transaction in their accounting system, such as the transaction amount, dates, status, and related account information.

Common scenarios where this node is beneficial include:

  • Correcting or updating transaction details after initial entry.
  • Linking transactions to other records for reconciliation.
  • Changing the status of a transaction (e.g., from Created to Booked).
  • Adding additional metadata like payment purpose or payee/payer name.

Practical example: A user imports bank transactions into sevDesk but later needs to update the amount or link the transaction to a different check account. This node can automate that update process within an n8n workflow.

Properties

Name Meaning
ID of Check Account Transaction The unique identifier of the check account transaction to update (required).
Additional Fields A collection of optional fields to update on the transaction:
- Value Date Date the transaction was booked.
- Amount Monetary value of the transaction.
- Check Account ID The ID of the check account to which this transaction belongs.
- Payee / Payer Name Name of the payee or payer involved in the transaction.
- Status Status of the transaction; options are: Created (100), Linked (200), Private (300), Booked (400).
- Entry Date Date when the transaction was imported.
- Payment Purpose Description or purpose of the payment.
- Enshrined Date indicating if the transaction has been enshrined (finalized and immutable).
- Source Transaction ID ID of the source transaction for rebooking purposes.
- Target Transaction ID ID of the target transaction for rebooking purposes.

Output

The node outputs JSON data representing the updated Check Account Transaction object as returned by the sevDesk API. This typically includes all the updated fields along with metadata such as IDs and timestamps.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the transaction, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the sevDesk API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://my.sevdesk.de/api/v1/.

Troubleshooting

  • Missing or invalid transaction ID: Ensure the "ID of Check Account Transaction" is provided and corresponds to an existing transaction.
  • Invalid field values: Dates must be valid ISO date strings; amounts should be numeric.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Status value errors: Use only the allowed status codes (100, 200, 300, 400).
  • Network issues: Confirm network connectivity to sevDesk API endpoint.

Common error messages might include unauthorized access, resource not found, or validation errors on input fields. Resolving these usually involves checking credentials, verifying IDs, and ensuring correct data formats.

Links and References

Discussion