Actions28
Overview
This node interacts with the Dolibarr API to list events stored in a Dolibarr system. It allows users to retrieve event records with flexible filtering, sorting, and pagination options. This is useful for scenarios where you want to integrate Dolibarr event data into workflows, such as syncing events with calendars, generating reports, or triggering actions based on event data.
Practical examples:
- Fetching all upcoming events sorted by date.
- Retrieving a limited number of recent events owned by specific users.
- Applying custom SQL filters to get events matching complex criteria.
Properties
| Name | Meaning |
|---|---|
| Sort Field | The database field used to sort the returned events (e.g., "t.id"). |
| Sort Order | The order of sorting: either ascending (ASC) or descending (DESC). |
| Limit | Maximum number of event records to return per request. |
| Page | The page number to query for paginated results (0-based index). |
| Get All | Whether to return all matching events ignoring the limit, or only up to the specified limit. |
| User IDs | Filter events by owner user IDs; can specify one or multiple IDs separated by commas. |
| SQL Filters | Additional SQL-like filter criteria to apply for more advanced querying of events. |
Output
The node outputs an array of JSON objects representing the events retrieved from Dolibarr. Each object corresponds to an event record with fields as defined by the Dolibarr API response.
If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals purely with JSON event data.
Dependencies
- Requires connection to a Dolibarr instance via its REST API.
- Needs an API authentication credential configured in n8n to access the Dolibarr API.
- The base URL of the Dolibarr API must be set in the credentials.
Troubleshooting
- Empty results: Check that the filters (User IDs, SQL Filters) are correctly formatted and match existing data.
- Authentication errors: Ensure the API key or token is valid and has sufficient permissions.
- Pagination issues: If using
Get Allset to false, verify theLimitandPageparameters to avoid missing data. - Invalid SQL filters: The SQL filter syntax must follow Dolibarr's expected format; incorrect syntax may cause errors or no results.
- API connectivity: Confirm the Dolibarr API endpoint is reachable and the base URL is correct.