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
The node integrates with the sevDesk API to update existing Credit Notes. It allows users to modify various fields of a Credit Note such as its number, contact details, date, status, texts, address, currency, and tax-related settings. This node is useful in scenarios where automated or bulk updates to credit notes are needed, for example, correcting information after issuance, updating statuses based on payment events, or adjusting tax rules due to regulatory changes.
Practical examples:
- Automatically marking a Credit Note as "Paid" after receiving payment confirmation.
- Updating the contact information linked to a Credit Note when customer details change.
- Changing the Credit Note date or adding header/footer text before sending it out.
Properties
| Name | Meaning |
|---|---|
| Credit Note ID | The unique identifier of the Credit Note to update. This is required to specify which Credit Note will be modified. |
| Update Fields | A collection of fields that can be updated on the Credit Note. These include: |
| - Credit Note Number | The new number to assign to the Credit Note. |
| - Contact | Contact information related to the Credit Note, including: • ID: Identifier of the contact. • Object Name: Typically "Contact". |
| - Credit Note Date | The date of the Credit Note (string format). |
| - Status | The status of the Credit Note. Possible values: • Draft (100) • Open (200) • Paid (1000) |
| - Header | Text to appear in the header section of the Credit Note. |
| - Head Text | Multiline text for the head section of the Credit Note. |
| - Foot Text | Multiline text for the footer section of the Credit Note. |
| - Address | Address associated with the Credit Note. |
| - Currency | Currency code used for the Credit Note. |
| - Tax Rule | VAT rule according to sevDesk API v2.0, replacing deprecated taxType. Options: • 1: Standard VAT liable transactions (0%, 7%, 19%) • 2: Exports (0%) • 3: Intra-community deliveries (0%, 7%, 19%) • 4: Tax-free transactions §4 UStG (0%) • 5: Reverse charge according to §13b UStG (0%) • 11: Tax not levied according to §19 UStG - Small business (0%) |
| - Tax Type (Deprecated) | Deprecated field for tax type; maintained only for backward compatibility. Users should prefer Tax Rule. |
| - Tax Text | Custom text describing the tax. |
| - Small Settlement | Boolean flag indicating if this is a small settlement. |
Output
The node outputs an array of JSON objects representing the response from the sevDesk API after attempting to update each specified Credit Note. Each output item corresponds to one input item processed.
- The
jsonfield contains the updated Credit Note data returned by the API. - If an error occurs during processing and the node is set to continue on failure, the output includes an
errorfield with the error message. - The node does not explicitly output binary data.
Dependencies
- Requires an active connection to the sevDesk API via an API key credential configured in n8n.
- The base URL for API requests is
https://my.sevdesk.de/api/with the API version dynamically set from credentials. - Environment configuration validation is performed at runtime to ensure proper setup.
Troubleshooting
Common issues:
- Invalid or missing Credit Note ID will cause the update operation to fail.
- Providing deprecated
taxTypewithouttaxRulemay lead to unexpected behavior; prefer usingtaxRule. - Incorrect status codes or invalid field formats can result in API errors.
- Network or authentication failures due to incorrect API credentials.
Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Typical error messages relate to authorization failures, invalid IDs, or malformed request payloads.
Resolutions:
- Verify the Credit Note ID exists and is correct.
- Ensure API credentials are valid and have sufficient permissions.
- Use supported values for status and tax rules.
- Check network connectivity and API endpoint accessibility.