Lexware icon

Lexware

Interact with the Lexware API
Join our community

Actions41

Overview

This node integrates with the Lexware API to perform various operations on different resources, including vouchers. Specifically, for the "Vouchers" resource and the "Get Many" operation, it retrieves multiple voucher records from Lexware. This is useful when you want to fetch a list of vouchers, optionally filtered by status or paginated by page number.

Practical examples include:

  • Retrieving all vouchers for reconciliation or reporting.
  • Filtering vouchers by their status (e.g., paid, pending) to process only relevant entries.
  • Paginating through large sets of vouchers to handle them in batches.

Properties

Name Meaning
Page The page number of the voucher list to retrieve. Used for pagination.
Status Optional filter to retrieve vouchers by their status. Possible values depend on Lexware's API but typically include statuses like "paid", "pending", etc.

Output

The node outputs an array of voucher objects in the json field. Each object represents a voucher record retrieved from Lexware, containing details such as voucher ID, date, amount, status, and other relevant fields as defined by the Lexware API.

If the node supports binary data output for vouchers (not explicitly shown in the provided code), it would typically represent attachments or scanned documents related to vouchers.

Dependencies

  • Requires an active connection to the Lexware API via an API key credential configured in n8n.
  • The node depends on the Lexware API being accessible and properly authenticated.
  • No additional external dependencies are indicated beyond the Lexware API.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Network connectivity problems preventing access to the Lexware API.
    • Invalid page numbers or status filters that do not match any vouchers, resulting in empty responses.

  • Error messages:

    • "Unsupported resource: vouchers" — This would occur if the resource parameter is incorrectly set; ensure "vouchers" is selected.
    • API errors returned from Lexware (e.g., rate limits, invalid parameters) will be propagated; check the API response for details.

  • Resolutions:

    • Verify API credentials and permissions.
    • Confirm network connectivity.
    • Use valid page numbers starting from 0 or 1 depending on API expectations.
    • Use correct status filter values as per Lexware documentation.

Links and References

Discussion