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 update a Contact Address record. It allows users to modify various fields of an existing contact address, such as street, zip code, city, and related identifiers like country or contact IDs. This is useful in scenarios where contact address details need to be kept current, for example, updating a customer's shipping or billing address after they move or change their contact information.
Practical examples include:
- Automatically updating customer addresses from form submissions.
- Synchronizing address changes from another CRM system.
- Correcting or enriching address data based on external inputs.
Properties
| Name | Meaning |
|---|---|
| Contact Address ID | The unique numeric identifier of the contact address to update (required). |
| Fields to Update | A collection of optional fields to modify in the contact address: |
| - Street | Street name of the address. |
| - Zip Code | Postal or zip code of the address. |
| - City | City name of the address. |
| - Category ID | Numeric category identifier indicating the type of address. Options include Work=43, Private=44, Empty=45, Invoice Address=47, Delivery Address=48, Pickup Address=49. |
| - Name in Address | First name or primary name associated with the address. |
| - Second Name in Address | Secondary name field for the address. |
| - Third Name in Address | Tertiary name field for the address. |
| - Fourth Name in Address | Quaternary name field for the address. |
| - Country ID | Unique numeric identifier of the country associated with the address. |
| - Contact ID | Unique numeric identifier of the contact linked to this address. |
Output
The node outputs JSON data representing the updated contact address object as returned by the sevDesk API. This typically includes all the fields of the contact address after the update operation, reflecting the new values.
If binary data were involved (not indicated here), it would represent file attachments or similar content related to the contact address, but this node focuses solely on JSON data updates.
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/. - Proper permissions on the API key to perform update operations on contact addresses.
Troubleshooting
- Missing or invalid Contact Address ID: The update will fail if the provided ID does not exist or is not specified. Ensure the ID is correct and present.
- Invalid field values: Providing incorrect types (e.g., string instead of number) or invalid references (nonexistent country or contact IDs) may cause errors.
- API authentication errors: If the API key is missing, expired, or lacks permissions, the request will be rejected.
- Network issues: Connectivity problems can prevent successful API calls.
Common error messages might include:
- "Not Found" or "404" if the contact address ID does not exist.
- "Unauthorized" or "401" if authentication fails.
- Validation errors specifying which fields are invalid.
To resolve these, verify input data correctness, ensure valid API credentials, and check network connectivity.