sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API to manage accounting contacts. Specifically, the "Create" operation under the "AccountingContact" resource allows users to add new accounting contact entries into their sevDesk account. This is useful for automating bookkeeping tasks such as adding new clients or vendors with their respective accounting identifiers.

Practical examples include:

  • Automatically creating a new accounting contact when a new customer signs up on an e-commerce platform.
  • Syncing vendor information from an external CRM system into sevDesk for streamlined invoice processing.

Properties

Name Meaning
Contact A collection of contact details including:
- Contact ID: The unique identifier of the contact to which this accounting contact belongs.
- Object Name: The type of object, fixed as "Contact".
Debitor Number The debitor number assigned to the accounting contact (used for accounts receivable).
Creditor Number The creditor number assigned to the accounting contact (used for accounts payable).

Output

The node outputs an array of JSON objects representing the results of the create operation(s). Each item in the output corresponds to one created accounting contact and contains the response data returned by the sevDesk API.

If an error occurs during creation and the node is configured to continue on failure, the output will include an object with an error field describing the issue for that particular item.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The base URL for API requests is https://my.sevdesk.de/api/{apiVersion}, where {apiVersion} is dynamically set based on the provided credentials.
  • The node depends on internal resource management and validation modules to handle API requests and input validation.

Troubleshooting

  • Common issues:

    • Missing or invalid API authentication token can cause authorization errors.
    • Providing incomplete or incorrect contact information may result in validation errors from the API.
    • Network connectivity problems can lead to request timeouts or failures.
  • Error messages:

    • Errors returned from the API are captured and included in the output if "continue on fail" is enabled.
    • Typical error messages might indicate missing required fields or invalid identifiers.
  • Resolution tips:

    • Ensure the API key credential is correctly configured and has sufficient permissions.
    • Verify all required fields, especially the Contact collection and debitor/creditor numbers, are properly filled.
    • Check network connectivity and retry if transient errors occur.

Links and References

Discussion