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 perform various operations related to exporting data. Specifically, the "Export DATEV (Deprecated)" operation allows users to export financial data in the DATEV format, which is commonly used for accounting and tax purposes in Germany. This operation supports legacy CSV and XML exports and includes options to customize the export scope and content.
Typical use cases include:
- Exporting accounting vouchers or transactions for tax filing.
- Generating export files for auditors or accountants.
- Automating periodic financial data exports from sevDesk into DATEV-compatible formats.
Properties
| Name | Meaning |
|---|---|
| Archive Documents | Whether to archive the documents after export (true/false). |
| Download | Whether to download the export file immediately (true/false). |
| End Date | The end date for the export period (string, typically in date format). |
| Enshrine Documents | Whether to enshrine (securely store) the documents during export (true/false). |
| Export By Payday | Whether to export data grouped by payday (true/false). |
| Hash | A hash string used for verifying or identifying the export job. |
| Include Document XML | Whether to include the document XML data in the export (true/false). |
| Include Enshrined | Whether to include previously enshrined documents in the export (true/false). |
| Include Exported Documents | Whether to include documents that have already been exported (true/false). |
| Job ID | Identifier of a specific export job to query or download (string). |
| Sev Query | A custom query string to filter or specify export data (string). |
| Start Date | The start date for the export period (string, typically in date format). |
| Stateless | Whether to perform the export statelessly, without saving state between requests (true/false). |
| Types | Comma-separated list of types of data to export (string). |
Output
The node outputs JSON data representing the result of the export operation. This may include:
- Status information about the export job.
- Metadata such as job IDs or hashes.
- Links or references to downloadable export files.
- Error messages if the operation fails.
If the "Download" option is enabled, the node may also output binary data corresponding to the exported file (e.g., CSV or ZIP archives), allowing direct file handling within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the sevDesk API.
- The node uses the base URL
https://my.sevdesk.de/api/combined with the configured API version. - Environment configuration validation is performed before execution.
- No additional external dependencies beyond the sevDesk API are required.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect date formats for "Start Date" or "End Date" may lead to errors or empty exports.
- Using deprecated export operations might result in warnings or limited support.
- Providing invalid job IDs or hashes can cause the node to fail when querying export status or downloads.
Error Messages:
- Errors returned from the API are captured and included in the output JSON under an
errorfield. - If "Continue On Fail" is enabled, the node will not stop on errors but will output error details per item.
- Validation schema initialization errors are logged to the console but do not prevent node execution.
- Errors returned from the API are captured and included in the output JSON under an
Resolution Tips:
- Verify API credentials and permissions.
- Ensure date strings follow expected formats (e.g., ISO 8601).
- Use supported export operations instead of deprecated ones when possible.
- Check job IDs and hashes for correctness before use.