Actions41
- AccountingContact Actions
- Category Actions
- CheckAccount Actions
- CheckAccountTransaction Actions
- CommunicationWay Actions
- Contact Actions
- ContactAddress Actions
- Invoice Actions
- Part Actions
Overview
This node integrates with the sevDesk API to create an Accounting Contact linked to a specific contact. It is useful for automating the management of accounting contacts within sevDesk, such as adding new accounting details related to customers or vendors in your accounting system.
Typical use cases include:
- Automatically creating accounting contact records when new contacts are added in your CRM.
- Synchronizing accounting-related identifiers like debitor or creditor numbers from other systems into sevDesk.
- Streamlining bookkeeping workflows by programmatically managing accounting contacts.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to which this accounting contact belongs. |
| Additional Fields | Optional extra fields to specify additional accounting contact details: |
| - Debitor Number | Numeric identifier representing the debitor number of the accounting contact. |
| - Creditor Number | Numeric identifier representing the creditor number of the accounting contact. |
Output
The node outputs JSON data representing the created accounting contact object as returned by the sevDesk API. This typically includes the newly assigned accounting contact ID and all submitted fields, confirming successful creation.
No binary data output is involved.
Dependencies
- Requires an active sevDesk API key credential configured in n8n to authenticate requests.
- Relies on the sevDesk REST API endpoint at
https://my.sevdesk.de/api/v1/.
Troubleshooting
- Missing or invalid Contact ID: The "Contact ID" property is required. Ensure it is provided and corresponds to an existing contact in sevDesk.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Invalid field values: Numeric fields like Debitor Number and Creditor Number must be valid numbers; otherwise, the API may reject the request.
- Network issues: Check connectivity to the sevDesk API endpoint if requests time out or fail.
Common error messages will generally come from the sevDesk API and indicate issues such as unauthorized access, missing required fields, or invalid data formats. Reviewing the API response message will help identify the exact cause.
Links and References
- sevDesk API Documentation (for detailed API usage and field definitions)