Actions41
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Actions
- ContactAddress Actions
- Invoice Actions
- Part Actions
Overview
The node integrates with the sevDesk API to mark an invoice as sent. This operation updates the status of a specified invoice, indicating that it has been delivered to the customer through a chosen method such as print, postal mail, email, or PDF download. It is useful in accounting and invoicing workflows where tracking the dispatch status of invoices is necessary for record-keeping and follow-up.
Practical examples include:
- Automatically marking invoices as sent after generating and printing them.
- Updating invoice status when sending invoices via postal service or email.
- Tracking when customers have downloaded their invoice PDFs.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique numeric identifier of the invoice to mark as sent. |
| Send Type | The method by which the invoice was sent to the customer. Options: "Print (VPR)", "Postal (VP)", "Mail (VM)", "Downloaded (VPDF)". |
| Send Draft | Boolean flag indicating whether the invoice should be enshrined (finalized) after marking it as sent. |
Output
The node outputs JSON data representing the updated invoice object as returned by the sevDesk API after marking it as sent. This typically includes the invoice's current status, send type, timestamps, and any other metadata related to the invoice state.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the sevDesk API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for API requests is
https://my.sevdesk.de/api/v1/.
Troubleshooting
- Invalid Invoice ID: If the provided invoice ID does not exist or is incorrect, the API may return an error indicating the invoice was not found. Verify the invoice ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is correctly set up in n8n.
- Invalid Send Type: Providing a send type outside the allowed options ("VPR", "VP", "VM", "VPDF") may result in request rejection. Use one of the predefined options.
- Network Issues: Connectivity problems with the sevDesk API endpoint can cause timeouts or failed requests. Check network access and API availability.
Links and References
- sevDesk API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general usage of custom nodes and credential setup)