Details
These events are created by specific triggers in certain applications. Most of these guarantee the resource ID in the hook data. The configurations for these events are specific and are not supported by all applications. Check the table below to see where the events are created from.List of tables and actions
|
pricelist_product_removed |
delete |
erply api |
Fired when a product is removed from a pricelist. |
|
assortment_product_woocomm |
delete |
new PIM (PIM api) |
Fired when a product is removed from an assortment. |
|
asssortment_product_woocomm |
insert, update and delete |
new PIM (PIM api) |
Fired on product to assortment adjustments. |
|
sales_document |
update |
erply api, bo classic, bo berlin |
Fired when an existing sales document is updated. |
|
cash_invoice |
insert |
erply api, bo classic, bo berlin |
Fired when a new receipt type sales document is created. Can be used to detect POS sales. |