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 to retrieve multiple credit notes based on specified filters. It is useful for automating financial workflows where you need to fetch batches of credit note data, such as generating reports, syncing accounting data, or auditing transactions.
For example, you can use this node to:
- Retrieve all credit notes issued to a specific contact within a date range.
- Filter credit notes by their status (Draft, Open, Paid) to process only those that require action.
- Extract credit note numbers for reconciliation purposes.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of optional filters to narrow down the credit notes retrieved: |
| - Contact ID | The unique identifier of the contact associated with the credit note. |
| - Credit Note Number | The specific credit note number to search for. |
| - Start Date | The start date to filter credit notes from (inclusive). |
| - End Date | The end date to filter credit notes up to (inclusive). |
| - Status | The status of the credit notes to retrieve. Options are: Draft (100), Open (200), Paid (1000). |
Output
The node outputs an array of JSON objects representing credit notes matching the provided filters. Each object contains the details of a credit note as returned by the sevDesk API.
If any errors occur during execution and the node is configured to continue on failure, the output will include error objects with messages describing the issue.
No binary data output is produced by this operation.
Dependencies
- Requires an active sevDesk API key credential configured in n8n.
- The node uses the sevDesk API endpoint
https://my.sevdesk.de/api/with the version specified in credentials. - Environment configuration validation is performed before execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect filter values (e.g., invalid dates or non-existent contact IDs) may result in empty results or API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors thrown by the API or network issues are caught and can be output as error JSON if "Continue On Fail" is enabled.
- Typical error messages include authentication failures, invalid parameters, or rate limiting notices.
Resolution tips:
- Verify API credentials and permissions.
- Ensure filter values conform to expected formats.
- Check network access and retry if transient errors occur.