Actions98
- Contact Actions
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Address Actions
- Contact Custom Field Actions
- Contact Custom Field Setting Actions
- Credit Note Actions
- Credit Note Po Actions
- Export Actions
- Update Export Config
- Export DATEV (Deprecated)
- Start DATEV CSV Zip Export
- Start DATEV XML Zip Export
- Generate Download Hash
- Get Progress
- Get Job Download Info
- Export Invoice as CSV
- Export Invoice as Zip
- Export Credit Note as CSV
- Export Voucher as CSV
- Export Voucher as Zip
- Export Transaction as CSV
- Export Contact as CSV
- Part Actions
- Invoice Actions
- Invoice Position Actions
- Order Actions
- Order Position Actions
- Report Actions
- Tag Actions
- Voucher Actions
- VoucherPo Actions
Overview
This node integrates with the sevDesk API, allowing users to interact with various sevDesk resources. Specifically, for the Category resource with the Get Many operation, it retrieves multiple category records from sevDesk based on optional filters. This is useful when you want to fetch a list of categories, for example, to display them in a dashboard, synchronize them with another system, or process them further in an automation workflow.
Practical examples include:
- Retrieving all categories related to contact addresses or parts.
- Filtering categories by object type to narrow down results.
- Using the retrieved categories to update inventory or customer data elsewhere.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters to apply when retrieving categories. |
| Object Type | The type of object to filter categories by. Options: "Contact Address", "Part". |
The Filters property allows specifying criteria to limit which categories are returned. For the Object Type filter, you can choose between:
- Contact Address
- Part
Output
The node outputs an array of JSON objects representing the categories retrieved from sevDesk. Each item corresponds to a category record and contains its properties as returned by the sevDesk API.
If an error occurs during execution and the node is configured to continue on failure, the output will include an object with an error field describing the issue, paired with the input item index.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the sevDesk API via an API key credential.
- The node uses the base URL
https://my.sevdesk.de/api/combined with the API version specified in credentials. - Environment configuration validation is performed before execution.
- Validation schemas for sevDesk data structures are initialized at runtime.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect filter values may result in empty responses or errors.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
- Errors thrown by the API (e.g., unauthorized, bad request) will be surfaced in the node's output if "Continue On Fail" is enabled.
- Initialization failures of validation schemas are logged to the console but do not stop node execution.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Double-check filter options for correctness.
- Ensure stable internet connection and access to the sevDesk API endpoint.
Links and References
- sevDesk API Documentation
- n8n documentation on creating custom nodes