Dolibarr Trigger icon

Dolibarr Trigger

Handle Dolibarr triggers via webhooks
Join our community

Overview

This node acts as a webhook trigger for Dolibarr, an open-source ERP and CRM system. It listens for specific events (triggers) from Dolibarr via webhooks and initiates workflows in n8n when those events occur. This is useful for automating processes based on changes or actions within Dolibarr, such as new invoices, updated contacts, or other business events.

Common scenarios include:

  • Automatically processing new orders or invoices created in Dolibarr.
  • Syncing customer data updates from Dolibarr to other systems.
  • Triggering notifications or follow-up tasks when certain Dolibarr events happen.

For example, you could configure this node to listen for the creation of new invoices and then automatically send an email notification or update a CRM record.

Properties

Name Meaning
Triggers Names or IDs Select one or more Dolibarr event triggers to listen for. You can choose from a list loaded dynamically or specify trigger IDs using expressions.

Output

The node outputs JSON data representing the webhook payload received from Dolibarr. The output structure corresponds directly to the body of the incoming HTTP POST request sent by Dolibarr when the specified event occurs.

  • The json output field contains an array with a single object representing the event data.
  • No binary data output is produced by this node.

Example output JSON structure:

[
  {
    "event": "invoice_created",
    "data": {
      "id": 123,
      "customer": "ACME Corp",
      "amount": 1000,
      ...
    }
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Dolibarr API.
  • Needs network access to receive incoming webhook requests from Dolibarr.
  • The node uses Dolibarr's REST API endpoints to manage webhook subscriptions (create, check existence, delete).
  • The user must configure Dolibarr to send webhook events to the URL provided by this node.

Troubleshooting

  • Webhook not triggering: Ensure that Dolibarr is correctly configured to send webhook events to the URL shown in the node’s webhook settings. Also, verify that the selected triggers match those supported by your Dolibarr instance.
  • Authentication errors: Confirm that the API key credential is valid and has sufficient permissions to manage webhooks and read event data.
  • Webhook creation/update failures: Check network connectivity and API endpoint availability. If the webhook already exists but is misconfigured, try deleting it manually or via the node and recreate it.
  • Empty or unexpected output: Verify that the Dolibarr event payload matches expected formats and that the correct triggers are selected.

Links and References

Discussion