Dolibarr icon

Dolibarr

Interact with Dolibarr API

Overview

This node interacts with the Dolibarr API to retrieve categories associated with a specific contact. It is useful when you want to fetch and analyze category data linked to contacts in your Dolibarr system, for example, to segment contacts by category or to display categorized contact information in workflows.

A practical use case would be automating marketing campaigns where contacts are grouped by categories, or generating reports that require categorization details of contacts.

Properties

Name Meaning
Contact ID The unique identifier (number) of the contact whose categories you want to retrieve.
Sort Field The field by which to sort the returned categories. Default is s.rowid.
Sort Order The order to sort the results: either ascending (ASC) or descending (DESC).
Limit Maximum number of category results to return.

Output

The node outputs JSON data containing the list of categories associated with the specified contact. Each item in the output JSON array represents a category object as returned by the Dolibarr API endpoint /contacts/{contactID}/categories.

The structure typically includes category identifiers, labels, and any other metadata provided by the API for each category.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to a Dolibarr instance via its REST API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL of the Dolibarr API must be set correctly in the credentials.

Troubleshooting

  • Invalid Contact ID: If the contact ID does not exist or is invalid, the API may return a 404 error. Verify the contact ID before running the node.
  • Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Ensure the API key/token is valid and has sufficient permissions.
  • Empty Results: If no categories are returned, confirm that the contact actually has categories assigned in Dolibarr.
  • Sorting Issues: Using an invalid sort field may result in errors or unexpected ordering. Use valid fields supported by the API, defaulting to s.rowid if unsure.
  • Limit Parameter: Setting the limit too high might impact performance; ensure it is reasonable based on expected data size.

Links and References

Discussion