sevDesk icon

sevDesk

Consume the sevDesk API
Join our community

Actions98

Overview

This node integrates with the sevDesk API to perform various operations on different resources. Specifically, for the Contact resource and the Get Number of Items operation, it retrieves the count of contact items stored in sevDesk. This is useful when you want to quickly know how many contacts exist without fetching all their details.

Practical examples include:

  • Displaying the total number of contacts in a dashboard.
  • Using the count to paginate or batch process contacts.
  • Monitoring growth or changes in the contact list over time.

Properties

Name Meaning
Contact ID The unique identifier of the contact for which the number of related items is retrieved.

Note: The property is required and must be provided as a string.

Output

The node outputs JSON data containing the result of the requested operation. For the "Get Number of Items" operation on the Contact resource, the output JSON will typically include a numeric count representing how many items are associated with the specified contact ID.

Example output structure (conceptual):

{
  "count": 123
}

If an error occurs during execution, the output JSON will contain an error field with the error message.

Dependencies

  • Requires an API key credential for authenticating with the sevDesk API.
  • The node uses the base URL https://my.sevdesk.de/api/ combined with the API version specified in credentials.
  • Environment configuration validation is performed before execution.

Troubleshooting

  • Common issues:

    • Missing or invalid Contact ID: The operation requires a valid contact identifier; ensure this is correctly set.
    • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
    • Network or API downtime: Check connectivity and sevDesk service status if requests fail.

  • Error messages:

    • Errors returned from the API will be included in the output JSON under the error field.
    • If the node is set to continue on failure, errors for individual items will not stop the workflow but will be reported per item.

Links and References

Discussion