Dolibarr connector
The Dolibarr connector exposes ERP objects already mapped in Knot Core: you work with invoices, third parties, orders, and more without writing SQL by hand.
🔌 Available verbs
Each Dolibarr node picks an object (e.g. customer invoice, third party) then an action:
| Action | Typical use |
|---|---|
| Get | Load one record by ID or filter |
| List | Browse a filtered list (pagination handled by the connector) |
| Create | Create a document or record |
| Update | Change fields after business validation |
| Delete | Logical or hard delete depending on the Dolibarr object |
Inspector fields come from typed introspection: FK pickers and dropdowns match Dolibarr.
🔌 Multi-entity
Knot respects the active entity (entity = $conf->entity). A workflow started on entity 1 never reads or writes entity 2 data.
🔌 Required Dolibarr permissions
The connector runs as the user who triggered the run (manual) or as the technical account configured for scheduled triggers. Dolibarr blocks an action if the role lacks the native right.
| Object (examples) | Rights to verify |
|---|---|
Third party (societe) | Read / create / edit third parties |
| Customer invoice | Read / create invoices |
| Order | Read / create orders |
| Product / service | Read products |
Full matrix: Dolibarr permissions.
🔌 Expressions and context
Map fields with {{ }} expressions: a previous node’s output feeds the next Dolibarr node’s ID or columns.
{{ nodes.fetch_invoice.output.id }}Edge format: source → target (not from / to except legacy import).
🔌 Example: follow-up after invoice creation
- Object event trigger on invoice create.
- Get third party linked to the invoice.
- Email node with a follow-up template.
- Logic If to skip when amount is zero.
Test with Simulate before activation.