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 update contact information. It allows users to modify various attributes of an existing contact by specifying the contact's unique ID and providing updated field values. This is useful in scenarios where contact details need to be kept current, such as updating customer records, correcting data entry errors, or adding new information like tax numbers or bank details.
Practical examples include:
- Updating a customer's birthday or academic title.
- Changing the organization's name or description.
- Adjusting payment-related settings like default discount or cashback percentages.
- Modifying tax-related information for compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update (required). |
| Academic Title | An academic title for the contact (not applicable for organizations). |
| Bank Account | Bank account number (IBAN) of the contact. |
| Bank Number | Bank number of the contact. |
| Birthday | Birthday of the contact (not applicable for organizations). |
| Customer Number | Customer number associated with the contact. |
| Default Cashback Percent | Percentage of invoice sum returned if invoices are paid on time. |
| Default Cashback Time | Time in days within which invoices must be paid to receive cashback. |
| Default Discount Amount | Default discount amount applied to every invoice (absolute or percentage based on another property). |
| Default Discount Percentage | Boolean indicating if the discount is a percentage (true) or absolute value (false). |
| Default Time To Pay | Payment goal in days set for every invoice of the contact. |
| Description | A textual description of the contact. |
| Exempt Vat | Boolean indicating if the contact is exempt from paying VAT. |
| Last Name (familyname) | Last name of the contact (not for organizations). |
| Gender | Gender of the contact (not for organizations). |
| Name | Organization name; presence indicates the contact is an organization. |
| Second Name (name2) | Second name of the contact (not for organizations). |
| Parent ID | Unique identifier of the parent contact. |
| First Name (surename) | First name of the contact (not for organizations). |
| Tax Number | Tax number of the contact. |
| Tax Office | Tax office responsible for the contact. |
| Tax Set ID | Identifier of the tax set used in every invoice of the contact. |
| Tax Type | Tax regulation type used by the contact; one of "default", "eu", "noteu", or "custom". |
| Title (titel) | Non-academic title for the contact (not for organizations). |
| Vat Number | VAT number of the contact. |
Output
The node outputs JSON data representing the updated contact object as returned by the sevDesk API. This typically includes all contact fields after the update operation, reflecting the new state of the contact record.
If binary data were involved (not indicated here), it would represent attachments or files related to the contact, but this node focuses solely on JSON contact data.
Dependencies
- Requires access to the sevDesk API endpoint
https://my.sevdesk.de/api/v1/. - Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses standard HTTP headers for JSON content negotiation.
Troubleshooting
- Invalid Contact ID: If the provided Contact ID does not exist, the API will likely return an error. Verify the ID before running the update.
- Missing Required Fields: Ensure that the Contact ID is provided since it is mandatory.
- Incorrect Field Types: For example, providing a string where a number is expected may cause request failures.
- API Authentication Errors: Check that the API key or token is valid and has sufficient permissions.
- Network Issues: Connectivity problems can prevent successful API calls.
- Field Restrictions: Some fields are not applicable for organizations (e.g., birthday, gender); setting these incorrectly might cause errors.
Links and References
- sevDesk API Documentation (general reference for API endpoints and data models)
- n8n documentation on creating custom nodes