sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to create a new contact address associated with an existing contact. It is useful in scenarios where you need to programmatically add or update address information for contacts within sevDesk, such as adding billing, shipping, or other categorized addresses.

Practical examples include:

  • Automatically adding a delivery address when a new order is placed.
  • Creating multiple categorized addresses (work, private, invoice) for a contact imported from another system.
  • Updating contact address details during CRM synchronization workflows.

Properties

Name Meaning
Contact ID Unique identifier of the Contact to which the address will be linked.
Country ID Unique identifier of the Country for the address.
Additional Fields Optional fields to specify more details about the address:
- Street Street name of the address.
- Zip Code Postal code of the address.
- City City name of the address.
- Category ID Category of the address; options include Work (43), Private (44), Empty (45), Invoice Address (47), Delivery Address (48), Pickup Address (49).
- Name in Address First name or main name used in 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.

Output

The node outputs JSON data representing the created contact address object as returned by the sevDesk API. This typically includes the newly assigned address ID and all submitted address details.

If binary data were involved (not indicated here), it would represent files or attachments related to the address, but this node focuses on JSON data only.

Dependencies

  • Requires an active sevDesk API key credential configured in n8n to authenticate requests.
  • The node sends HTTP requests to the sevDesk API endpoint at https://my.sevdesk.de/api/v1/.

Troubleshooting

  • Missing Required Fields: Ensure that both Contact ID and Country ID are provided; these are mandatory.
  • Invalid Category ID: Use one of the predefined category IDs (e.g., 43 for Work) to avoid errors.
  • Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • API Rate Limits or Network Issues: If requests fail intermittently, check network connectivity and sevDesk API rate limits.
  • Unexpected API Responses: Confirm that the input data types match expected formats (e.g., numbers for IDs, strings for text fields).

Links and References

Discussion