sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to update a specific Communication Way entity. A Communication Way represents a method of contacting or communicating with a contact, such as an email address, phone number, or website.

The "Update Communication Way" operation allows users to modify details of an existing communication method by specifying its unique identifier and the fields to change. This is useful in scenarios where contact information needs to be kept current, for example:

  • Updating a contact's primary email address.
  • Changing the phone number associated with a contact.
  • Marking a communication way as the main one for a contact.
  • Adjusting the category/type of the communication method (e.g., from Work to Mobile).

Practical examples include CRM systems syncing updated contact info, customer support tools maintaining accurate contact channels, or marketing platforms managing communication preferences.

Properties

Name Meaning
Communication Way ID Unique identifier of the Communication Way to update.
Fields to Update Collection of optional fields to modify:
- Contact ID Unique identifier of the Contact associated with this communication way.
- Main Boolean indicating if this is the main communication way for the contact.
- Communication Way Key ID Identifier representing the category of the communication way. Options include:
Private=1, Work=2, Fax=3, Mobile=4, Empty=5, Autobox=6, Newsletter=7, Invoice Address=8
- Communication Way Type Type of communication method. Possible values:
Email, Phone, Web, Mobile
- Value The actual value of the communication way, e.g., phone number, email address, or website URL.

Output

The node outputs JSON data representing the updated Communication Way object as returned by the sevDesk API. This typically includes all properties of the communication way after the update, such as its ID, type, value, associated contact, and flags like whether it is the main communication method.

No binary data output is involved in this operation.

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/.
  • Proper network connectivity to sevDesk's API service is necessary.

Troubleshooting

  • Invalid Communication Way ID: If the specified ID does not exist, the API will return an error. Verify that the ID is correct and corresponds to an existing communication way.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
  • Validation Errors: Providing invalid field values (e.g., unsupported communication way type) may result in errors. Confirm that all fields conform to expected formats and allowed options.
  • Permission Issues: The API user must have sufficient permissions to update communication ways.
  • Network Issues: Connectivity problems can cause request failures. Check internet access and firewall settings.

Links and References

Discussion