sevDesk icon

sevDesk

Consume the sevDesk API

Overview

This node integrates with the sevDesk API to retrieve multiple contact addresses based on specified filters. It is useful for scenarios where you need to fetch a list of contact addresses, such as syncing contact data, generating reports, or managing address records in bulk.

For example, you can use this node to:

  • Retrieve all contact addresses associated with a particular contact.
  • Paginate through contact addresses by specifying limits and offsets.
  • Filter contact addresses by their unique ID.

Properties

Name Meaning
Filters A collection of parameters to filter the contact addresses returned. Options include:
- Contact Address ID Retrieve all contact addresses matching this specific ID.
- Limit Maximum number of results to return (minimum 1, default 50).
- Offset Number of results to skip for pagination purposes (minimum 1, default 50).

The "Filters" property allows flexible querying of contact addresses using these fields.

Output

The node outputs JSON data representing an array of contact address objects retrieved from the sevDesk API. Each object contains details about a contact address, such as its ID, street, city, postal code, and other relevant address information.

No binary data output is produced by 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/v1/.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Using an invalid Contact Address ID filter may result in no data returned.
    • Pagination parameters (limit and offset) set incorrectly (e.g., less than 1) may cause request failures.
  • Error messages:

    • Authentication errors typically indicate problems with the API key; verify and update credentials.
    • HTTP 404 errors when filtering by Contact Address ID suggest that the specified ID does not exist.
    • Validation errors on limit or offset values require adjusting these parameters to valid ranges.

Links and References

Discussion