Actions41
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Actions
- ContactAddress Actions
- Invoice Actions
- Part Actions
Overview
This node integrates with the sevDesk API to retrieve multiple check account records. It is designed to fetch a list of check accounts, optionally filtered and paginated according to user-defined parameters. This functionality is useful in scenarios where users need to synchronize or analyze financial account data from sevDesk within their workflows, such as generating reports, auditing accounts, or feeding accounting data into other systems.
For example, a user might want to retrieve all check accounts with a specific ID or limit the number of results returned for performance reasons.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of parameters to filter and paginate the retrieved check accounts: |
- ID of Check Account (checkAccountId) |
Filter by a specific check account ID to retrieve a single account. |
- Limit (limit) |
Maximum number of results to return (minimum 1, default 50). |
- Offset (offset) |
Number of records to skip for pagination (minimum 1, default 50). |
Output
The node outputs JSON data representing the retrieved check accounts from the sevDesk API. The structure typically includes an array of check account objects, each containing details such as account ID, name, balance, and other relevant financial information as provided by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the sevDesk API.
- Users must provide valid API authentication credentials (an API key or token) configured in n8n.
- The node uses the base URL
https://my.sevdesk.de/api/v1/for API requests.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid check account ID may result in no data returned or an error.
- Exceeding API rate limits could lead to temporary request failures.
- Incorrect pagination parameters (e.g., negative numbers) may cause errors or unexpected results.
Error Messages:
- Authentication errors usually indicate issues with the API key/token; verify and update credentials.
- "Not Found" errors when filtering by ID suggest the specified check account does not exist.
- Validation errors on
limitoroffsetparameters indicate values outside allowed ranges; ensure they are positive integers.
Links and References
- sevDesk API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)