sevDeskInstall

Overview

This node integrates with the sevDesk API to perform various operations on different resources. Specifically, for the CommunicationWay resource with the Get operation, it retrieves detailed information about a specific communication way identified by its unique ID. This is useful in scenarios where you need to fetch contact methods such as phone numbers, email addresses, or other communication channels associated with entities managed in sevDesk.

Practical examples include:

• Retrieving a customer's preferred communication method before sending notifications.
• Fetching details of a communication channel to update or verify contact information.
• Integrating communication data into workflows that require up-to-date contact details.

Properties

Output

The node outputs JSON data representing the communication way object retrieved from the sevDesk API. The structure typically includes fields such as the ID, type (e.g., phone, email), value (e.g., phone number or email address), and possibly metadata related to the communication way.

If the node encounters an error during execution and "Continue On Fail" is enabled, the output will contain an error message under the json.error field paired with the corresponding input item index.

No binary data output is produced by this operation.

Dependencies

• Requires an active connection to the sevDesk API via an API key credential configured in n8n.
• The node depends on the sevDesk API being accessible at https://my.sevdesk.de/api/.
• Environment configuration validation is performed before execution to ensure necessary environment variables or settings are correctly set.

Troubleshooting

• Common issues:

  • Invalid or missing Communication Way ID will cause the API call to fail.
  • Network connectivity problems or incorrect API credentials can prevent successful API requests.
  • If the specified communication way does not exist, the API will return an error.

• Error messages:

  • Errors returned from the API are captured and can be output if "Continue On Fail" is enabled.
  • Typical errors include authentication failures, resource not found, or invalid parameters.

• Resolution tips:

  • Verify the Communication Way ID is correct and exists in sevDesk.
  • Ensure the API key credential is valid and has sufficient permissions.
  • Check network connectivity and API endpoint accessibility.
  • Enable "Continue On Fail" to handle errors gracefully within workflows.

Links and References

• sevDesk API Documentation
• n8n Documentation on Creating Custom Nodes