sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to retrieve multiple check account transactions based on various filter criteria. It is useful for financial workflows where users need to fetch transaction data from their check accounts, such as for reconciliation, reporting, or auditing purposes.

Typical use cases include:

  • Retrieving all transactions within a specific date range.
  • Filtering transactions by payment purpose or payee/payer name.
  • Fetching only booked transactions or filtering by credit/debit type.
  • Paginating through large sets of transactions using limit and offset parameters.

For example, a user could configure this node to get all booked debit transactions from a particular check account in the last month to generate a spending report.

Properties

Name Meaning
Filters A collection of fields to filter the transactions returned. Includes:
- Transaction ID Filter by a specific transaction's unique ID.
- Check Account ID Filter transactions belonging to a specific check account.
- Is Booked Boolean flag to retrieve only booked transactions (true) or not (false).
- Payment Purpose Filter transactions by their payment purpose description.
- Start Date Retrieve transactions from this date onwards.
- End Date Retrieve transactions up to this date.
- Payee / Payer Name Filter transactions by the name of the payee or payer.
- Credit Only Boolean flag to retrieve only credit transactions.
- Debit Only Boolean flag to retrieve only debit transactions.
- Limit Maximum number of results to return (pagination). Minimum 1, default 50.
- Offset Number of results to skip for pagination. Minimum 1, default 50.

Output

The node outputs an array of transaction objects in the json output field. Each object represents a check account transaction matching the specified filters. The structure typically includes details such as transaction ID, amount, booking status, payment purpose, dates, payee/payer information, and whether it is a credit or debit.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the sevDesk API via an API key credential.
  • The node uses the base URL https://my.sevdesk.de/api/v1/ for API requests.
  • Proper API authentication credentials must be configured in n8n for successful requests.

Troubleshooting

  • Empty Results: If no transactions are returned, verify that the filter criteria are correct and that transactions exist matching those filters.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Pagination Issues: When using limit and offset, ensure values are set correctly to avoid missing or duplicate records.
  • Date Format: Dates should be provided in a valid ISO 8601 format; otherwise, the API may reject the request.
  • Conflicting Filters: Using both onlyCredit and onlyDebit as true simultaneously may result in no data; use them exclusively.

Links and References

Discussion