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 Delivery Notes. Specifically, for the Delivery Note - Create operation, it allows users to create new delivery note records in their Lexware Office system.

Typical use cases include automating the creation of delivery notes when orders are processed or shipped, ensuring that documentation is consistently generated and stored without manual intervention. For example, after an e-commerce order is fulfilled, this node can automatically create a delivery note reflecting the shipment details.

Properties

Name Meaning
Additional Fields A collection of optional fields to add extra information to the delivery note. Options include: Name, Description, Notes, Tags, External ID.

The "Additional Fields" property lets you specify extra metadata about the delivery note being created, such as a custom name or description, any notes, tags for categorization, or an external identifier for integration with other systems.

Output

The node outputs a JSON array where each element represents the created delivery note resource as returned by the Lexware Office API. The structure includes all standard fields of a delivery note as defined by the API, plus any additional fields provided during creation.

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 and API key from the configured credentials.
  • No other external dependencies or environment variables are required.

Troubleshooting

  • Missing Required Fields Error: If mandatory fields for creating a delivery note are not provided, the node throws an error listing the missing fields. Ensure all required fields are set before execution.
  • 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 Connectivity Issues: Network problems or incorrect base URL settings can cause request failures. Confirm the resource URL in credentials and network connectivity.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output array.

Links and References

Discussion