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 accounting contact records based on specified filters. It is useful for scenarios where you need to fetch a list of accounting contacts, such as syncing contact data from sevDesk into another system, generating reports, or performing bulk operations on contacts.
For example, you can use this node to:
- Retrieve all accounting contacts associated with a specific contact ID.
- Fetch a limited number of accounting contacts for pagination purposes.
- Filter accounting contacts by their unique accounting contact ID.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of parameters to filter the accounting contacts returned by the query. |
| - Accounting Contact ID | Retrieve all accounting contacts with this specific accounting contact ID (number). |
| - Contact ID | Retrieve all accounting contacts linked to this contact ID (number). |
| - Limit | Maximum number of results to return (number, minimum 1, default 50). |
| - Offset | Number of records to skip for pagination (number, minimum 1, default 50). |
Output
The node outputs JSON data containing an array of accounting contact objects matching the applied filters. Each object represents an accounting contact record retrieved from the sevDesk API.
If binary data were supported, it would typically represent attachments or files related to the contacts, but this node focuses on JSON data only.
Dependencies
- Requires an active sevDesk API key credential configured in n8n to authenticate requests.
- The node sends HTTP GET requests to the sevDesk API endpoint
https://my.sevdesk.de/api/v1/AccountingContact. - Proper network access to the sevDesk API is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Using invalid filter values (e.g., non-numeric IDs) may result in request failures.
- Exceeding API rate limits could lead to temporary blocking or errors.
- Pagination parameters (
limitandoffset) must be positive integers; otherwise, the API might reject the request.
Error messages:
- Authentication errors usually indicate incorrect or expired API keys; verify and update credentials.
- "Not Found" errors when using specific IDs suggest that no matching accounting contacts exist.
- Validation errors on parameters mean the input values do not meet expected formats or ranges.
Links and References
- sevDesk API Documentation – Official API docs for detailed information on endpoints and parameters.
- n8n Documentation – For guidance on setting up credentials and using HTTP request nodes.