Actions6
Overview
This node integrates with the Letter Xpress API to retrieve a list of financial transactions related to your Letter Xpress account. It supports filtering transactions by type (all, deposits, withdrawals, or print jobs) and paginating through results. This is useful for accounting, auditing, or monitoring payment flows within your Letter Xpress usage.
Practical examples:
- Fetch all recent transactions to reconcile payments.
- Retrieve only deposit transactions to track incoming funds.
- Get payout transactions to monitor money leaving your account.
- List print job transactions to analyze costs associated with printing services.
Properties
| Name | Meaning |
|---|---|
| Seite (page) | Page number for pagination of transaction results. Default is 1. |
| Transaktions Filter (transactionFilter) | Filter transactions by type: - Alle (All) - Einzahlungen (Deposits) - Auszahlungen (Withdrawals) - Aufträge (Print Jobs) |
Output
The node outputs an array of JSON objects representing transactions retrieved from the Letter Xpress API. Each object corresponds to a single transaction and contains details as provided by the API, such as transaction type, amount, date, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Letter Xpress API.
- The node makes HTTP requests to
https://api.letterxpress.de/v3/transactions. - Proper configuration of the API authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Requesting pages beyond available data may return empty results.
- Using unsupported filter values could lead to errors or no data returned.
Error messages:
- Errors thrown by the node typically wrap HTTP or API errors. For example, "Operation 'getTransactions' not supported" indicates a misconfiguration of the operation parameter.
- Network or API errors are surfaced as node API errors; ensure network connectivity and valid API keys.
Resolution tips:
- Verify that the API key credential is correctly set up and has required permissions.
- Use valid page numbers starting at 1.
- Select filters from the provided options only.
Links and References
- Letter Xpress API Documentation (general reference, actual URL may vary)
- n8n documentation on HTTP Request Node for understanding API calls in workflows