sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions41

Overview

This node integrates with the sevDesk API to retrieve multiple communication ways associated with contacts or other entities. Specifically, the "CommunicationWay" resource with the "Get Many" operation allows users to fetch a list of communication methods such as email addresses, phone numbers, web links, or mobile numbers.

Common scenarios include:

  • Extracting all contact emails or phone numbers for marketing campaigns.
  • Synchronizing communication details from sevDesk into another CRM or database.
  • Filtering communication ways by type or specific contact IDs to target communications effectively.

For example, a user might want to get all email addresses linked to a particular contact ID or retrieve the first 50 phone numbers stored in sevDesk.

Properties

Name Meaning
Filters A collection of parameters to filter the communication ways returned.
├─ Communication Way ID Retrieve communication ways matching this specific ID (number).
├─ Contact ID Retrieve communication ways associated with this contact ID (number).
├─ Type Filter communication ways by type. Options: Email, Phone, Web, Mobile.
├─ Limit Maximum number of results to return (minimum 1, default 50).
└─ Offset Number of records to skip for pagination (minimum 1, default 50).

Output

The node outputs an array of JSON objects representing communication ways. Each object typically contains fields such as the communication way's ID, type (email, phone, etc.), and associated contact information.

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

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The node uses the base URL https://my.sevdesk.de/api/v1/ for all requests.
  • Proper configuration of the API credential within n8n is necessary.

Troubleshooting

  • Empty Results: If no communication ways are returned, verify that the filters (e.g., contact ID or type) match existing data in sevDesk.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
  • Pagination Issues: Adjust the limit and offset properties carefully; setting offset too high may result in empty responses.
  • Invalid Filter Values: Using unsupported types or invalid IDs can cause errors or no data returned.

Links and References

Discussion