sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to create a new Communication Way entry for a contact. A Communication Way represents a method of communication such as email, phone, web address, or mobile number associated with a contact in sevDesk.

Common scenarios where this node is useful include:

  • Adding a new email or phone number to a contact's profile.
  • Registering multiple communication methods for a client or vendor.
  • Updating contact information by adding additional communication channels.

For example, you might use this node to add a work email and a mobile phone number to a customer record automatically when onboarding new clients.

Properties

Name Meaning
Communication Way Key ID Unique 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 The type of communication method. Options are:
Email, Phone, Web, Mobile
Value The actual value of the communication way, e.g., the phone number, email address, or website URL
Additional Fields Optional extra fields:
- Contact ID: Unique identifier of the contact to associate this communication way with
- Main: Boolean indicating if this is the main communication way for the contact

Output

The node outputs JSON data representing the created Communication Way object as returned by the sevDesk API. This typically includes identifiers, the communication type, value, and metadata such as whether it is marked as the main communication method.

No binary data output is involved.

Dependencies

  • Requires an active sevDesk API key credential configured in n8n.
  • The node sends requests to the sevDesk API endpoint at https://my.sevdesk.de/api/v1/.
  • Proper permissions on the API key to create Communication Way entries are necessary.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key is correctly set up and has permissions to create communication ways.
  • Invalid Communication Way Key ID: Use one of the predefined numeric IDs (e.g., 1 for Private, 2 for Work). Using unsupported values may cause errors.
  • Invalid Communication Way Type: Must be one of the allowed options (EMAIL, PHONE, WEB, MOBILE).
  • Contact ID not found: If specifying a Contact ID, ensure it exists in sevDesk; otherwise, the creation will fail.
  • API rate limits or network issues: May cause request failures; check connectivity and sevDesk API status.

Links and References

Discussion