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 details of a specific part in an inventory or product catalog. It allows users to modify various attributes of a part such as its name, pricing, stock levels, category, and other metadata.
This node is beneficial in scenarios where automated synchronization or batch updates of product parts are needed, for example:
- Updating pricing information after a cost change.
- Adjusting stock quantities based on new inventory data.
- Adding internal comments or changing the status of parts programmatically.
- Modifying part categories or units of measurement in bulk.
Practical example: An e-commerce business could use this node to update multiple parts' prices and stock levels nightly based on supplier data feeds.
Properties
| Name | Meaning |
|---|---|
| Part ID | The unique identifier of the part to update. Required. |
| Additional Fields | A collection of optional fields to update on the part. These include: |
| - Category: JSON object specifying the category of the part. | |
| - Internal Comment: Text comment visible internally but not on invoices/orders. | |
| - Name: The name of the part. | |
| - Part Number: The part's identifying number/code. | |
| - Price: Net selling price of the part. | |
| - Price Gross: Gross selling price (including tax). | |
| - Price Net: Net selling price (redundant with Price). | |
| - Price Purchase: Purchase cost of the part. | |
| - Status: Numeric status code (e.g., 50 = Inactive, 100 = Active). | |
| - Stock: Current stock quantity. | |
| - Stock Enabled: Boolean indicating if stock tracking is enabled. | |
| - Tax Rate: Applicable tax rate percentage. | |
| - Text: Descriptive text about the part. | |
| - Unity: JSON object defining the unit of measurement for the part. |
Output
The node outputs an array of JSON objects representing the updated part(s) returned from the sevDesk API. Each output item contains the updated part data reflecting the changes made.
If errors occur during execution and "continue on fail" is enabled, the output will include error objects with messages describing the failure for each affected item.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the sevDesk API.
- The base URL for API requests is
https://my.sevdesk.de/api/with a configurable API version. - Environment configuration validation is performed before execution.
- Uses internal resource manager classes to handle API operations.
Troubleshooting
Common issues:
- Invalid or missing Part ID will cause the update to fail.
- Providing invalid JSON structures for complex fields like Category or Unity may result in API errors.
- Network or authentication failures due to incorrect API credentials.
- Attempting to update read-only or restricted fields may be rejected by the API.
Error messages:
- Errors returned from the API are captured and can be output per item if "continue on fail" is enabled.
- Validation schema initialization errors are logged at startup; ensure environment variables and configurations are correct.
Resolutions:
- Verify that all required fields, especially Part ID, are correctly set.
- Ensure JSON fields are properly formatted.
- Confirm API credentials and permissions.
- Use "continue on fail" cautiously to handle partial failures gracefully.
Links and References
- sevDesk API Documentation
- n8n documentation on Creating Custom Nodes
- General REST API best practices for error handling and authentication