Actions61
- Contact Actions
- Article Actions
- Voucher Actions
- Invoice Actions
- Down Payment Invoice Actions
- Quotation Actions
- Credit Note Actions
- Delivery Note Actions
- Dunning Actions
- File Actions
- Profile Actions
- Country Actions
- Payment Condition Actions
- Event Subscription Actions
- Recurring Template Actions
- Voucherlist Actions
- Trigger Actions
Overview
This node integrates with the Lexware Office API, allowing users to interact with various Lexware resources such as contacts, articles, invoices, payment conditions, and more. Specifically, for the Payment Condition resource with the Get operation, the node retrieves detailed information about a specific payment condition by its ID.
Typical use cases include:
- Fetching payment terms or conditions associated with invoices or orders.
- Automating workflows that require validation or retrieval of payment condition details.
- Integrating Lexware payment conditions into other business processes or systems.
Example: You want to retrieve the details of a payment condition by its ID to check the payment terms before processing an invoice.
Properties
| Name | Meaning |
|---|---|
| Payment Condition ID | The unique identifier of the payment condition to retrieve. This is a required string. |
Output
The node outputs a JSON array where each item corresponds to the retrieved payment condition data from Lexware Office API. The structure of the JSON object matches the payment condition resource schema provided by Lexware, typically including fields like ID, name, terms, description, and other relevant attributes.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- No additional external dependencies are required beyond the configured Lexware Office API credentials.
Troubleshooting
- Missing Required Fields Error: If the required "Payment Condition ID" is not provided, the node will throw an error indicating missing required fields.
- Authentication Errors: Ensure that the API key credential is correctly configured and valid; otherwise, API calls will fail.
- Resource Not Found: If the provided Payment Condition ID does not exist, the API may return an error or empty response.
- API Rate Limits: The node respects rate limits configured in credentials; exceeding these may cause temporary failures.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Creating Custom Nodes