Difference between revisions of "Interfaces Dolibarr toward foreign systems"
Jump to navigation
Jump to search
m Tag: 2017 source edit |
m Tag: 2017 source edit |
||
| Line 10: | Line 10: | ||
* [[Triggers]] - a mechanism to activate your own code when Dolibarr executes an action (for example, creation of invoice, edit of a user, delete of an order, ...) | * [[Triggers]] - a mechanism to activate your own code when Dolibarr executes an action (for example, creation of invoice, edit of a user, delete of an order, ...) | ||
| − | * [[Module | + | * [[Module WebHook]] - a module to send a JSON message on a Dolibarr triggered event. |
* [[Hooks system]] - an interface to integrate your own code in an entry point of Dolibarr | * [[Hooks system]] - an interface to integrate your own code in an entry point of Dolibarr | ||
For more information on the opposite mechanism (allow an external system to interface with the Dolibarr system and use the Dolibarr's datas), see [[Interfaces from foreign systems toward Dolibarr]]. | For more information on the opposite mechanism (allow an external system to interface with the Dolibarr system and use the Dolibarr's datas), see [[Interfaces from foreign systems toward Dolibarr]]. | ||
Revision as of 11:52, 24 May 2023
Dolibarr provides several mechanisms to interface Dolibarr with an external system on the behave of a Dolibarr event :
- Triggers - a mechanism to activate your own code when Dolibarr executes an action (for example, creation of invoice, edit of a user, delete of an order, ...)
- Module WebHook - a module to send a JSON message on a Dolibarr triggered event.
- Hooks system - an interface to integrate your own code in an entry point of Dolibarr
For more information on the opposite mechanism (allow an external system to interface with the Dolibarr system and use the Dolibarr's datas), see Interfaces from foreign systems toward Dolibarr.