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 create new orders. It allows users to specify detailed order information including customer contact, order date, status, and multiple order positions (line items). This node is useful in automating order creation workflows, such as when syncing orders from an e-commerce platform or CRM into sevDesk for accounting and fulfillment purposes.
Practical examples:
- Automatically creating a new order in sevDesk when a customer places an order on your website.
- Syncing orders from another system into sevDesk to maintain consistent records.
- Creating draft orders that can later be updated or finalized within sevDesk.
Properties
| Name | Meaning |
|---|---|
| Order | Collection of fields describing the order details: |
| - Address | The address associated with the order. |
| - Contact ID | The unique identifier of the contact (customer) for whom the order is created. Required |
| - Contact Person ID | Identifier for a specific contact person related to the order. |
| - Foot Text | Custom text to appear at the bottom of the order document. |
| - Head Text | Custom text to appear at the top of the order document. |
| - Header | Header text for the order document. |
| - Order Date | The date and time when the order was placed. Required |
| - Order ID | Identifier for the order (optional, usually for updates). |
| - Order Number | A custom order number string. |
| - Status | Current status of the order. Options include: Draft, Delivered, Billed, Accepted, Declined, Finished. Default is Draft. |
| Order Positions | Multiple line items for the order, each containing: |
| - Discount | Discount applied to the position (number). |
| - Part ID | Identifier of the part/product being ordered. |
| - Position Number | Numeric position/order of the item in the list. |
| - Price | Price per unit for the position. |
| - Quantity | Number of units ordered. Defaults to 1. |
Output
The node outputs an array of JSON objects representing the response from the sevDesk API after creating the order(s). Each output item corresponds to one input item processed.
The json field contains the created order data returned by the API, which typically includes the order's unique ID, status, and other metadata confirming successful creation.
If the node encounters errors during execution and "Continue On Fail" is enabled, it outputs an error object with the error message under the json.error property paired with the corresponding input item index.
This node does not output binary data.
Dependencies
- Requires an active sevDesk API key credential configured in n8n.
- Uses the sevDesk API endpoint at
https://my.sevdesk.de/api/with the specified API version. - Environment configuration validation is performed before execution to ensure required environment variables or settings are present.
Troubleshooting
Common issues:
- Missing required fields such as Contact ID or Order Date will cause the API request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Incorrectly formatted dates or invalid status values may cause validation errors.
- Network connectivity issues can prevent communication with the sevDesk API.
Error messages:
- Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
- Validation schema initialization failure logs an error to the console but does not stop node execution.
Resolutions:
- Ensure all required properties are provided and correctly formatted.
- Verify API credentials and permissions.
- Check network connectivity and API endpoint accessibility.
- Enable "Continue On Fail" to handle partial failures gracefully.