31,029
edits
mNo edit summary Tag: 2017 source edit |
mNo edit summary Tag: 2017 source edit |
||
| Line 10: | Line 10: | ||
Dolibarr provides several mechanisms to interface Dolibarr with an external system on the behave of a Dolibarr event : | 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, ...) | * [[Triggers system]] - 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, ...) | ||
* [[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 | ||
* [[Module Webhook]] - a module to send a JSON message on a Dolibarr triggered event. | * [[Module Webhook]] - a module to send a JSON message on a Dolibarr triggered event. | ||
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]]. | ||