Actions28
Overview
The node integrates with the Dolibarr API to create new events within the Dolibarr system. It is designed to facilitate adding event records programmatically, which can be useful for automating workflows that involve scheduling, logging, or tracking activities related to users or other entities in Dolibarr.
Common scenarios include:
- Automatically creating an event when a user performs a specific action in another system.
- Logging interactions or tasks assigned to a user.
- Scheduling reminders or notifications linked to a user or entity.
For example, you might use this node to create an event of type "AC_OTH_AUTO" (a generic event type) associated with a particular owner user ID whenever a certain trigger occurs in your workflow.
Properties
| Name | Meaning |
|---|---|
| Owner ID | The numeric ID of the owner user to whom the event will be linked. Must be a positive integer. |
| Type Code | The code representing the type of event to create. Default is "AC_OTH_AUTO". |
| Fields | A collection of additional event fields to set. This allows specifying other event attributes beyond owner and type code. |
Output
The node outputs the full response from the Dolibarr API after creating the event. The main output is a JSON object containing the details of the newly created event as returned by the API.
No binary data output is involved.
Dependencies
- Requires access to a Dolibarr instance with its REST API enabled.
- Needs an API authentication token or key configured in n8n credentials to authorize requests to the Dolibarr API.
- The base URL of the Dolibarr API must be provided in the credentials configuration.
Troubleshooting
- Invalid Owner ID: If the owner ID does not correspond to an existing user in Dolibarr, the API may return an error. Verify the owner ID before running the node.
- Authentication Errors: Ensure the API key or token is valid and has sufficient permissions to create events.
- Incorrect Type Code: Using an invalid or unsupported event type code may cause the API to reject the request.
- Network Issues: Connectivity problems between n8n and the Dolibarr server will prevent successful event creation.
- Missing Required Fields: The node requires at least the owner ID and type code; missing these will cause errors.
Links and References
- Dolibarr Official API Documentation
- Dolibarr Events Module (for understanding event types and usage)