Lexware Office icon

Lexware Office

Interact with Lexware Office API

Actions61

Overview

This node integrates with the Lexware Office API to retrieve payment condition data. Specifically, the "Get All" operation for the "Payment Condition" resource fetches multiple payment conditions from the system, supporting pagination, sorting, and limiting the number of results.

Use cases include:

  • Retrieving all available payment terms configured in Lexware Office for use in invoicing or financial workflows.
  • Synchronizing payment condition data into other systems or databases.
  • Filtering and sorting payment conditions to find specific terms based on creation date, update date, name, or ID.

Example: You want to list all payment conditions sorted by creation date descending, returning only the first 50 entries for display or further processing.

Properties

Name Meaning
Return All Whether to return all results or limit the number of results.
Limit Maximum number of results to return (only used if Return All is false). Range: 1 to 250.
Page Page number for pagination (0-based index).
Sort Sort order for results. Options:
- Created At (Ascending)
- Created At (Descending)
- Updated At (Ascending)
- Updated At (Descending)
- Voucher Date (Ascending)
- Voucher Date (Descending)
- Name (Ascending)
- Name (Descending)
- ID (Ascending)
- ID (Descending)
Cursor Cursor string for cursor-based pagination (optional).
Offset Offset number for offset-based pagination (optional).

These properties allow flexible control over how many payment conditions are retrieved and how they are ordered.

Output

The node outputs an array of JSON objects representing payment conditions retrieved from Lexware Office.

  • Each object corresponds to a single payment condition with its associated fields as provided by the API.
  • The output is returned as JSON in the json field of the output data.
  • No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Lexware Office API.
  • The node uses the base URL and API key from the provided credentials to make requests.
  • No additional external dependencies are required beyond the Lexware Office API access.

Troubleshooting

  • Missing Required Fields Error: If required parameters are missing for an operation, the node throws an error listing missing fields. Ensure all mandatory fields are provided.
  • API Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify that the API key credential is correctly configured.
  • Pagination Issues: When using pagination properties (page, limit, cursor, offset), ensure values are within valid ranges to avoid empty or unexpected results.
  • Rate Limits: The Lexware Office API may enforce rate limits; excessive requests might be throttled. Adjust workflow frequency accordingly.

Links and References

Discussion