Actions10
- Contacts Endpoint Actions
- Invoices Endpoint Actions
- Files Endpoint Actions
Overview
This node interacts with the LexOffice API, specifically targeting the "Invoices Endpoint" resource. The "Retrieve an Invoice" operation allows users to fetch detailed information about a specific invoice by providing its unique Invoice ID. This is useful for automating accounting workflows, synchronizing invoice data between systems, or retrieving invoice details for reporting and analysis.
Practical examples:
- Automatically fetching invoice details after a new invoice is created in LexOffice.
- Integrating LexOffice invoices into another system (e.g., CRM, ERP) for unified financial tracking.
- Retrieving invoice data for custom notifications or document generation.
Properties
| Name | Type | Meaning |
|---|---|---|
| Invoice ID | String | The unique identifier of the invoice to retrieve. Required to specify which invoice's details should be fetched from LexOffice. |
Output
The output will be a JSON object containing all available details of the requested invoice. The structure typically includes fields such as invoice number, date, customer information, line items, totals, status, and other metadata provided by the LexOffice API for an invoice.
Example output structure:
{
"id": "string",
"invoiceNumber": "string",
"status": "string",
"createdDate": "string",
"customer": { /* ... */ },
"lineItems": [ /* ... */ ],
"totalAmount": "number",
// ...other invoice fields
}
Note: The exact fields depend on the LexOffice API response.
Dependencies
- External Service: Requires access to the LexOffice API.
- API Key: You must configure valid LexOffice API credentials in n8n under the credential type
lexOfficeApi. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid or missing Invoice ID: If the provided Invoice ID does not exist or is empty, the API will return an error.
- Authentication errors: If the LexOffice API credentials are missing or invalid, requests will fail with authentication errors.
- Network/API downtime: If LexOffice is unreachable, the node will throw connection errors.
Common error messages and resolutions:
"404 Not Found": The specified Invoice ID does not exist. Double-check the ID."401 Unauthorized": Invalid or missing API credentials. Ensure your LexOffice API key is correctly configured in n8n."400 Bad Request": The Invoice ID format may be incorrect or missing. Make sure you provide a valid string.