Lexware Office icon

Lexware Office

Interact with Lexware Office API

Actions61

Overview

This node integrates with the Lexware Office API to manage various business resources, including invoices. Specifically, for the Invoice - Create operation, it allows users to create new invoices by specifying essential invoice details such as the contact ID, invoice date, due date, currency, and language. This is useful in automating invoice generation workflows within business processes, such as billing customers after order fulfillment or generating invoices based on sales data.

Practical examples include:

  • Automatically creating an invoice when a new order is placed in an e-commerce system.
  • Generating invoices for recurring services with specified due dates and currencies.
  • Creating invoices in different languages and currencies for international clients.

Properties

Name Meaning
Contact ID ID of the contact (customer) for whom the invoice is created.
Invoice Date The date when the invoice is issued.
Due Date The payment due date for the invoice.
Currency Currency code for the invoice amounts (default is EUR).
Language Language code for the invoice (default is German "de").
Additional Fields Optional additional fields including: Name, Description, Notes, Tags, External ID.

Output

The node outputs a JSON array where each element represents the result of the create operation for an invoice. The JSON object contains the details of the newly created invoice as returned by the Lexware Office API.

If multiple input items are processed, the output will be an array of invoice objects corresponding to each input.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Lexware Office API.
  • The node uses the base URL provided in the credentials to send requests to the Lexware Office API.
  • No other external dependencies are required.

Troubleshooting

  • Missing Required Fields Error: If required fields like Contact ID are not provided, the node throws an error listing missing fields. Ensure all mandatory properties are set.
  • Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify that the API key is correctly configured in the node credentials.
  • API Endpoint Issues: If the resource URL in credentials is incorrect or unreachable, requests will fail. Confirm the base URL is correct and accessible.
  • Rate Limits: The API may enforce rate limits; if exceeded, requests might be rejected. Consider adjusting request frequency or handling retries.

Links and References


If you need details on other operations or resources, feel free to ask!

Discussion